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-j8x7-qcw4-xx85
|
2023-01-30T18:17:35Z
|
2023-01-26T21:30:25Z
| null |
['CVE-2022-25847']
|
Cross-site Scripting (XSS) in serve-lite
|
All versions of the package serve-lite are vulnerable to Cross-site Scripting (XSS) because when it detects a request to a directory, it renders a file listing of all of its contents with links that include the actual file names without any sanitization or output encoding.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'serve-lite'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-25847'}, {'type': 'WEB', 'url': 'https://gist.github.com/lirantal/52debd25284726fcc2eaed9c7512975c'}, {'type': 'PACKAGE', 'url': 'https://github.com/beenotung/serve-lite'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-SERVELITE-3149915'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-30T18:17:35Z', 'nvd_published_at': '2023-01-26T21:15:00Z'}
|
1.4.0
|
GHSA-f85w-wvc7-crwc
|
2023-01-20T21:54:22Z
|
2023-01-20T21:54:22Z
| null |
[]
|
bumpalo has use-after-free due to a lifetime error in `Vec::into_iter()`
|
In affected versions of this crate, the lifetime of the iterator produced by `Vec::into_iter()` is not constrained to the lifetime of the `Bump` that allocated the vector's memory. Using the iterator after the `Bump` is dropped causes use-after-free accesses.
The following example demonstrates memory corruption arising from a misuse of this unsoundness.
```rust
use bumpalo::{collections::Vec, Bump};
fn main() {
let bump = Bump::new();
let mut vec = Vec::new_in(&bump);
vec.extend([0x01u8; 32]);
let into_iter = vec.into_iter();
drop(bump);
for _ in 0..100 {
let reuse_bump = Bump::new();
let _reuse_alloc = reuse_bump.alloc([0x41u8; 10]);
}
for x in into_iter {
print!("0x{:02x} ", x);
}
println!();
}
```
The issue was corrected in version 3.11.1 by adding a lifetime to the `IntoIter` type, and updating the signature of `Vec::into_iter()` to constrain this lifetime.
|
[]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'bumpalo'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.1.0'}, {'fixed': '3.11.1'}]}]}]
|
[{'type': 'PACKAGE', 'url': 'https://github.com/fitzgen/bumpalo'}, {'type': 'WEB', 'url': 'https://github.com/fitzgen/bumpalo/blob/main/CHANGELOG.md#3111'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2022-0078.html'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T21:54:22Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q79m-c546-2g63
|
2023-01-20T23:23:26Z
|
2023-01-20T23:23:26Z
| null |
[]
|
CakePHP vulnerable to Denial of Service attack through XML payloads
|
RequestHandlerComponent had a vulnerability that would allow well crafted requests to create a denial of service attack. RequestHandlerComponent leverages `Xml::build()` which allows reading local files. We recommend that all applications using RequestHandlerComponent upgrade, or disable parsing XML payloads.
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.6'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.0.99'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.1.0'}, {'fixed': '2.1.99'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.2.0'}, {'fixed': '2.2.99'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.3.0'}, {'fixed': '2.3.99'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.99'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.90'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.6'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cakephp/cakephp/commit/c186487151356a8d7c6e2cae05f87b9df0e59fbb'}, {'type': 'WEB', 'url': 'https://bakery.cakephp.org/2015/05/28/cakephp_2_6_6_and_3_0_6_released.html'}, {'type': 'WEB', 'url': 'https://github.com/FriendsOfPHP/security-advisories/blob/master/cakephp/cakephp/2015-05-28.yaml'}, {'type': 'PACKAGE', 'url': 'https://github.com/cakephp/cakephp'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:23:26Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9vvw-cc9w-f27h
|
2023-01-13T17:19:08Z
|
2023-01-09T12:30:19Z
| null |
['CVE-2017-20165']
|
debug Inefficient Regular Expression Complexity vulnerability
|
A vulnerability classified as problematic has been found in debug-js debug up to 3.0.x. This affects the function useColors of the file src/node.js. The manipulation of the argument str leads to inefficient regular expression complexity. Upgrading to version 3.1.0 is able to address this issue. The name of the patch is c38a0166c266a679c8de012d4eaccec3f944e685. It is recommended to upgrade the affected component. The identifier VDB-217665 was assigned to this vulnerability. The patch has been backported to the 2.6.x branch in version 2.6.9.
|
[{'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': 'npm', 'name': 'debug'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.1.0'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'debug'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.6.9'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2017-20165'}, {'type': 'WEB', 'url': 'https://github.com/debug-js/debug/pull/504'}, {'type': 'WEB', 'url': 'https://github.com/debug-js/debug/commit/c38a0166c266a679c8de012d4eaccec3f944e685'}, {'type': 'PACKAGE', 'url': 'https://github.com/debug-js/debug'}, {'type': 'WEB', 'url': 'https://github.com/debug-js/debug/releases/tag/2.6.9'}, {'type': 'WEB', 'url': 'https://github.com/debug-js/debug/releases/tag/3.1.0'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.217665'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.217665'}]
|
{'cwe_ids': ['CWE-1333'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T21:49:01Z', 'nvd_published_at': '2023-01-09T10:15:00Z'}
|
1.4.0
|
GHSA-g4r8-28fp-f255
|
2023-01-11T23:48:32Z
|
2023-01-05T12:30:27Z
| null |
['CVE-2020-36641']
|
aXMLRPC XML External Entity vulnerability
|
A vulnerability classified as problematic was found in gturri aXMLRPC up to 1.12.0. This vulnerability affects the function `ResponseParser` of the file `src/main/java/de/timroes/axmlrpc/ResponseParser.java`. The manipulation leads to xml external entity reference. Upgrading to version 1.12.1 is able to address this issue. The name of the patch is ad6615b3ec41353e614f6ea5fdd5b046442a832b. It is recommended to upgrade the affected component. VDB-217450 is the identifier assigned to this vulnerability.
|
[{'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': 'Maven', 'name': 'fr.turri:aXMLRPC'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.12.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36641'}, {'type': 'WEB', 'url': 'https://github.com/gturri/aXMLRPC/commit/ad6615b3ec41353e614f6ea5fdd5b046442a832b'}, {'type': 'PACKAGE', 'url': 'https://github.com/gturri/aXMLRPC'}, {'type': 'WEB', 'url': 'https://github.com/gturri/aXMLRPC/releases/tag/aXMLRPC-1.12.1'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.217450'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.217450'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-11T23:48:32Z', 'nvd_published_at': '2023-01-05T12:15:00Z'}
|
1.4.0
|
GHSA-jxgp-jgh3-8jc8
|
2023-01-24T23:29:09Z
|
2023-01-09T21:57:54Z
| null |
['CVE-2023-22480']
|
KubeOperator allows unauthorized access to system API
|
### Summary
Unauthorized access refers to the ability to bypass the system's preset permission settings to access some API interfaces. The attack exploits a flaw in how online applications handle routing permissions.
### Affected Version
<= v3.16.3
### Patches
The vulnerability has been fixed in v3.16.3.
https://github.com/KubeOperator/KubeOperator/commit/7ef42bf1c16900d13e6376f8be5ecdbfdfb44aaf
### Workarounds
It is recommended to upgrade the version to v3.16.4.
### For more information
If you have any questions or comments about this advisory, please open an issue.
### References
https://github.com/KubeOperator/KubeOperator/releases/tag/v3.16.4
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/KubeOperator/KubeOperator'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '3.16.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/KubeOperator/KubeOperator/security/advisories/GHSA-jxgp-jgh3-8jc8'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22480'}, {'type': 'WEB', 'url': 'https://github.com/KubeOperator/KubeOperator/commit/7ef42bf1c16900d13e6376f8be5ecdbfdfb44aaf'}, {'type': 'PACKAGE', 'url': 'https://github.com/KubeOperator/KubeOperator'}, {'type': 'WEB', 'url': 'https://github.com/KubeOperator/KubeOperator/releases/tag/v3.16.4'}]
|
{'cwe_ids': ['CWE-285', 'CWE-863'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-09T21:57:54Z', 'nvd_published_at': '2023-01-14T01:15:00Z'}
|
1.4.0
|
GHSA-77h8-5j3h-jcjf
|
2023-02-08T22:32:36Z
|
2023-01-31T18:30:23Z
| null |
['CVE-2023-24162']
|
Dromara Hutool Deserialization of Untrusted Data vulnerability
|
Deserialization vulnerability in Dromara Hutool v5.8.11 allows attacker to execute arbitrary code via the XmlUtil.readObjectFromXml parameter.
|
[{'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': 'Maven', 'name': 'cn.hutool:hutool-all'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '5.8.11'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24162'}, {'type': 'WEB', 'url': 'https://github.com/dromara/hutool/issues/2855'}, {'type': 'PACKAGE', 'url': 'https://gitee.com/dromara/hutool'}, {'type': 'WEB', 'url': 'https://gitee.com/dromara/hutool/issues/I6AEX2'}]
|
{'cwe_ids': ['CWE-502'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-02-08T22:32:36Z', 'nvd_published_at': '2023-01-31T16:15:00Z'}
|
1.4.0
|
GHSA-22m9-m3ww-53h3
|
2023-01-19T21:31:41Z
|
2023-01-10T22:19:49Z
| null |
['CVE-2023-22487']
|
Flarum post mentions can be used to read any post on the forum without access control
|
Using the mentions feature provided by the flarum/mentions extension, users can mention any post ID on the forum with the special `@"<username>"#p<id>` syntax.
The following behavior never changes no matter if the actor should be able to read the mentioned post or not:
A URL to the mentioned post is inserted into the actor post HTML, leaking its discussion ID and post number.
The `mentionsPosts` relationship included in the `POST /api/posts` and `PATCH /api/posts/<id>` JSON responses leaks the full JSON:API payload of all mentioned posts without any access control. This includes the content, date, number and attributes added by other extensions.
An attacker only needs the ability to create new posts on the forum to exploit the vulnerability. This works even if new posts require approval. If they have the ability to edit posts, the attack can be performed even more discreetly by using a single post to scan any size of database and hiding the attack post content afterward.
### Impact
The attack allows the leaking of all posts in the forum database, including posts awaiting approval, posts in tags the user has no access to, and private discussions created by other extensions like FriendsOfFlarum Byobu. This also includes non-comment posts like tag changes or renaming events.
The discussion payload is not leaked but using the mention HTML payload it's possible to extract the discussion ID of all posts and combine all posts back together into their original discussions even if the discussion title remains unknown.
All Flarum versions prior to `v1.6.3` are affected.
### Patches
The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum have to upgrade as soon as possible to v1.6.3 using:
```
composer update --prefer-dist --no-dev -a -W
```
You can then confirm you run the latest version using:
```
composer show flarum/core
```
### Workarounds
Disable the mentions extension.
### For more information
For any questions or comments on this vulnerability please visit https://discuss.flarum.org/
For support questions create a discussion at https://discuss.flarum.org/t/support.
A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing [security@flarum.org](mailto:security@flarum.org), and we will address it promptly.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'flarum/mentions'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.6.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/flarum/framework/security/advisories/GHSA-22m9-m3ww-53h3'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22487'}, {'type': 'WEB', 'url': 'https://github.com/flarum/framework/commit/ab1c868b978e8b0d09a5d682c54665dae17d0985'}, {'type': 'PACKAGE', 'url': 'https://github.com/flarum/framework'}, {'type': 'WEB', 'url': 'https://github.com/flarum/framework/releases/tag/v1.6.3'}]
|
{'cwe_ids': ['CWE-284'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T22:19:49Z', 'nvd_published_at': '2023-01-11T20:15:00Z'}
|
1.4.0
|
GHSA-xr8h-wj4v-rx7f
|
2023-02-03T20:35:21Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24453']
|
Missing permission check in Jenkins TestQuality Updater Plugin
|
A missing check in Jenkins TestQuality Updater Plugin 1.3 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified username and password.
|
[{'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': 'Maven', 'name': 'org.jenkins-ci.plugins:testquality-updater'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24453'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2800'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T00:58:38Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-ccf4-9hjc-xxc4
|
2023-02-02T17:14:50Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24436']
|
Missing permission check in Jenkins GitHub Pull Request Builder Plugin allows enumerating credentials IDs
|
A missing permission check in Jenkins GitHub Pull Request Builder Plugin 1.42.2 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
|
[{'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.jenkins-ci.plugins:ghprb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.42.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24436'}, {'type': 'PACKAGE', 'url': 'https://github.com/jenkinsci/ghprb-plugin'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2789%20(1)'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:09:02Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-vg5x-6q66-rvgx
|
2023-01-13T21:05:08Z
|
2023-01-08T18:30:25Z
| null |
['CVE-2016-15015']
|
Barzahlen Payment Module PHP SDK vulnerable to Observable Timing Discrepancy
|
A vulnerability, which was classified as problematic, was found in viafintech Barzahlen Payment Module PHP SDK up to 2.0.0. Affected is the function `verify` of the file `src/Webhook.php`. The manipulation leads to observable timing discrepancy. Upgrading to version 2.0.1 is able to address this issue. The name of the patch is 3e7d29dc0ca6c054a6d6e211f32dae89078594c1. It is recommended to upgrade the affected component. VDB-217650 is the identifier assigned to this vulnerability.
|
[{'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': 'barzahlen/barzahlen-php'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2016-15015'}, {'type': 'WEB', 'url': 'https://github.com/viafintech/Barzahlen-PHP/pull/8'}, {'type': 'WEB', 'url': 'https://github.com/viafintech/Barzahlen-PHP/commit/3e7d29dc0ca6c054a6d6e211f32dae89078594c1'}, {'type': 'PACKAGE', 'url': 'https://github.com/viafintech/Barzahlen-PHP'}, {'type': 'WEB', 'url': 'https://github.com/viafintech/Barzahlen-PHP/releases/tag/v2.0.1'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.217650'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.217650'}]
|
{'cwe_ids': ['CWE-203', 'CWE-208'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-13T21:05:08Z', 'nvd_published_at': '2023-01-08T18:15:00Z'}
|
1.4.0
|
GHSA-96jv-r488-c2rj
|
2023-01-13T17:18:40Z
|
2023-01-10T03:30:29Z
| null |
['CVE-2023-22895']
|
bzip2 allows attackers to cause a denial of service via a large file that triggers an integer overflow
|
The bzip2 crate before 0.4.4 for Rust allow attackers to cause a denial of service via a large file that triggers an integer overflow in `mem.rs`. NOTE: this is unrelated to the https://crates.io/crates/bzip2-rs product.
|
[{'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': 'bzip2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.4.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22895'}, {'type': 'WEB', 'url': 'https://github.com/alexcrichton/bzip2-rs/pull/86'}, {'type': 'WEB', 'url': 'https://github.com/alexcrichton/bzip2-rs/commit/90c9c182cd5a5ebc75810aebd89b347a7bdf590b'}, {'type': 'WEB', 'url': 'https://crates.io/crates/bzip2/versions'}, {'type': 'PACKAGE', 'url': 'https://github.com/alexcrichton/bzip2-rs'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MI5SVRSGKBWB2JGDLDVIFY5ZQVDZP6I7/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SQK57GGXJX3AH7KF6S7S3N7JC5QOYUQ7/'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UUK2JO25PPA6XBREKJRBLRCD22LKIOLO/'}, {'type': 'WEB', 'url': 'https://rustsec.org/advisories/RUSTSEC-2023-0004.html'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T22:10:17Z', 'nvd_published_at': '2023-01-10T01:15:00Z'}
|
1.4.0
|
GHSA-vp2x-3mc3-3cj4
|
2023-01-31T19:01:51Z
|
2023-01-31T12:30:24Z
| null |
['CVE-2023-0591']
|
Path traversal in ubi-reader
|
ubireader_extract_files is vulnerable to path traversal when run against specifically crafted UBIFS files, allowing the attacker to overwrite files outside of the extraction directory (provided the process has write access to that file or directory). This is due to the fact that a node name (dent_node.name) is considered trusted and joined to the extraction directory path during processing, then the node content is written to that joined path. By crafting a malicious UBIFS file with node names holding path traversal payloads (e.g. ../../tmp/outside.txt), it's possible to force ubi_reader to write outside of the extraction directory. This issue affects ubi-reader before 0.8.5.
|
[{'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': 'ubi-reader'}, 'ecosystem_specific': {'affected_functions': ['ubireader.ubifs.output.extract_dents']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.8.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0591'}, {'type': 'WEB', 'url': 'https://github.com/jrspruitt/ubi_reader/pull/57'}, {'type': 'WEB', 'url': 'https://github.com/jrspruitt/ubi_reader/commit/d5d68e6b1b9f7070c29df5f67fc060f579ae9139'}, {'type': 'PACKAGE', 'url': 'https://github.com/jrspruitt/ubi_reader'}, {'type': 'WEB', 'url': 'https://onekey.com/blog/security-advisory-remote-command-execution-in-binwalk/'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-31T19:01:51Z', 'nvd_published_at': '2023-01-31T10:15:00Z'}
|
1.4.0
|
GHSA-q84x-3476-8ff2
|
2023-01-12T16:49:59Z
|
2023-01-06T12:31:34Z
| null |
['CVE-2022-45787']
|
Apache James MIME4J vulnerable to information disclosure to local users
|
Unproper laxist permissions on the temporary files used by MIME4J TempFileStorageProvider may lead to information disclosure to other local users. This issue affects Apache James MIME4J version 0.8.8 and prior versions. We recommend users to upgrade to MIME4j version 0.8.9 or later.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.james:apache-mime4j'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.8.9'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-45787'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/james-mime4j'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/26s8p9stl1z261c4qw15bsq03tt7t0rj'}]
|
{'cwe_ids': ['CWE-200', 'CWE-312'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-09T20:15:28Z', 'nvd_published_at': '2023-01-06T10:15:00Z'}
|
1.4.0
|
GHSA-59qg-93jg-236f
|
2023-01-20T23:18:17Z
|
2023-01-20T23:18:17Z
| null |
['CVE-2023-22732']
|
Shopware has Insufficient Session Expiration in Administration
|
### Impact
The Administration session expiration was set to one week, when an attacker has stolen the session cookie they could use it for a long period of time.
### Patches
We added an automatic logout into the Administration, so the user will be logged out when they are inactive.
### References
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-01-2023?category=security-updates
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'shopware/platform'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.18.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.18.0'}}, {'package': {'ecosystem': 'Packagist', 'name': 'shopware/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.18.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.18.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/shopware/platform/security/advisories/GHSA-59qg-93jg-236f'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22732'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/commit/cd7a89cbcd3a0428c6d1ef27b3aa15467a722ff6'}, {'type': 'WEB', 'url': 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-01-2023?category=security-updates'}, {'type': 'PACKAGE', 'url': 'https://github.com/shopware/platform'}]
|
{'cwe_ids': ['CWE-613'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:18:17Z', 'nvd_published_at': '2023-01-17T22:15:00Z'}
|
1.4.0
|
GHSA-6325-6g32-7p35
|
2023-01-26T23:57:52Z
|
2023-01-26T23:57:52Z
| null |
['CVE-2013-2513']
|
flash_tool Gem for Ruby File Download Handling Arbitrary Command Execution
|
flash_tool Gem for Ruby contains a flaw that is triggered during the handling of downloaded files that contain shell characters. With a specially crafted file, a context-dependent attacker can execute arbitrary commands.
|
[]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'flash_tool'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.6.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2013-2513'}, {'type': 'PACKAGE', 'url': 'https://github.com/milboj/flash_tool'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/flash_tool/CVE-2013-2513.yml'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-26T23:57:52Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-x9q4-qwfh-9gjq
|
2023-02-06T16:44:09Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24427']
|
Session fixation vulnerability in Jenkins Bitbucket OAuth Plugin
|
Jenkins Bitbucket OAuth Plugin 0.12 and earlier does not invalidate the previous session on login.
|
[{'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': 'Maven', 'name': 'org.jenkins-ci.plugins:bitbucket-oauth'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.13'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24427'}, {'type': 'WEB', 'url': 'https://github.com/jenkinsci/bitbucket-oauth-plugin/commit/b73ac285f8cfcc9727f089c6b2c7f13412285e7c'}, {'type': 'PACKAGE', 'url': 'https://github.com/jenkinsci/bitbucket-oauth-plugin'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2982'}]
|
{'cwe_ids': ['CWE-384'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:09:22Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-mf6x-hrgr-658f
|
2023-02-07T23:18:23Z
|
2023-01-30T06:30:27Z
| null |
['CVE-2022-25967']
|
Eta vulnerable to Code Injection via templates rendered with user-defined data
|
Versions of the package eta before 2.0.0 are vulnerable to Remote Code Execution (RCE) by overwriting template engine configuration variables with view options received from The Express render API. **Note:** This is exploitable only for users who are rendering templates with user-defined data.
|
[{'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': 'npm', 'name': 'eta'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-25967'}, {'type': 'WEB', 'url': 'https://github.com/eta-dev/eta/commit/5651392462ee0ff19d77c8481081a99e5b9138dd'}, {'type': 'PACKAGE', 'url': 'https://github.com/eta-dev/eta'}, {'type': 'WEB', 'url': 'https://github.com/eta-dev/eta/blob/9c8e4263d3a559444a3881a85c1607bf344d0b28/src/compile-string.ts%23L21'}, {'type': 'WEB', 'url': 'https://github.com/eta-dev/eta/blob/9c8e4263d3a559444a3881a85c1607bf344d0b28/src/file-handlers.ts%23L182'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-ETA-2936803'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-02-01T01:34:42Z', 'nvd_published_at': '2023-01-30T05:15:00Z'}
|
1.4.0
|
GHSA-g29v-5pwh-wxx4
|
2023-02-06T16:39:45Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24439']
|
Plaintext Storage of a Password in Jenkins JIRA Pipeline Steps Plugin
|
Jenkins JIRA Pipeline Steps Plugin 2.0.165.v8846cf59f3db and earlier stores the private keys unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.plugins:jira-steps'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.0.165.v8846cf59f3db'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24439'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2774'}]
|
{'cwe_ids': ['CWE-256', 'CWE-312'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:00:15Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-2pj2-gchf-wmw7
|
2023-01-27T17:41:12Z
|
2023-01-10T03:30:29Z
| null |
['CVE-2023-22899']
|
Zip4j Origin Validation Error
|
Zip4j through 2.11.2, as used in Threema and other products, does not always check the MAC when decrypting a ZIP archive. This issue has been fixed in version 2.11.3.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'net.lingala.zip4j:zip4j'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.11.3'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.11.2'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22899'}, {'type': 'WEB', 'url': 'https://github.com/srikanth-lingala/zip4j/issues/485'}, {'type': 'WEB', 'url': 'https://breakingthe3ma.app'}, {'type': 'WEB', 'url': 'https://breakingthe3ma.app/files/Threema-PST22.pdf'}, {'type': 'PACKAGE', 'url': 'https://github.com/srikanth-lingala/zip4j'}, {'type': 'WEB', 'url': 'https://github.com/srikanth-lingala/zip4j/releases'}, {'type': 'WEB', 'url': 'https://github.com/srikanth-lingala/zip4j/releases/tag/v2.11.3'}, {'type': 'WEB', 'url': 'https://news.ycombinator.com/item?id=34316206'}, {'type': 'WEB', 'url': 'https://threema.ch/en/blog/posts/news-alleged-weaknesses-statement'}]
|
{'cwe_ids': ['CWE-346'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-13T21:34:45Z', 'nvd_published_at': '2023-01-10T02:15:00Z'}
|
1.4.0
|
GHSA-wj79-9fxj-j86p
|
2023-02-03T20:39:34Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24447']
|
Cross-site request forgery vulnerability in Jenkins RabbitMQ Consumer Plugin
|
A cross-site request forgery (CSRF) vulnerability in Jenkins RabbitMQ Consumer Plugin 2.8 and earlier allows attackers to connect to an attacker-specified AMQP(S) URL using attacker-specified username and password.
|
[{'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.plugins:rabbitmq-consumer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.8'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24447'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2778'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T00:59:50Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-8r6h-m72v-38fg
|
2023-01-25T18:03:33Z
|
2023-01-17T23:57:23Z
| null |
['CVE-2023-22730']
|
Shopware vulnerable to Improper Input Validation of Clearance sale in cart
|
### Impact
It is possible to put the same line item multiple one in the cart using API, the Cart Validators checked the line item's individuality and the user was able to skip the clearance sale in cart
### Patches
The problem has been fixed with 6.4.18.1
### Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version. Or disable the newsletter registration completely.
### References
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-01-2023?category=security-updates
|
[{'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': 'Packagist', 'name': 'shopware/platform'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.18.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.18.0'}}, {'package': {'ecosystem': 'Packagist', 'name': 'shopware/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.18.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.18.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/shopware/platform/security/advisories/GHSA-8r6h-m72v-38fg'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22730'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/commit/4fce12096e54b2033832d9104fa2e68888c2b4e9'}, {'type': 'WEB', 'url': 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-01-2023?category=security-updates'}, {'type': 'PACKAGE', 'url': 'https://github.com/shopware/platform'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-17T23:57:23Z', 'nvd_published_at': '2023-01-17T22:15:00Z'}
|
1.4.0
|
GHSA-3mpg-q26j-83j5
|
2023-01-31T01:41:32Z
|
2023-01-21T03:30:28Z
| null |
['CVE-2020-36655']
|
Command injection in yiisoft/yii2-gii
|
Yii Yii2 Gii before 2.2.2 allows remote attackers to execute arbitrary code via the Generator.php messageCategory field. The attacker can embed arbitrary PHP code into the model file.
|
[{'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': 'Packagist', 'name': 'yiisoft/yii2-gii'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.2.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36655'}, {'type': 'WEB', 'url': 'https://github.com/yiisoft/yii2-gii/issues/433'}, {'type': 'WEB', 'url': 'https://github.com/yiisoft/yii2-gii/commit/ed61e0d85f43e23f79d7c9d1b4e5e5c09a32ce4b'}, {'type': 'PACKAGE', 'url': 'https://github.com/yiisoft/yii2-gii'}, {'type': 'WEB', 'url': 'https://lab.wallarm.com/yii2-gii-remote-code-execution/'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-23T20:42:57Z', 'nvd_published_at': '2023-01-21T01:15:00Z'}
|
1.4.0
|
GHSA-hph3-hv3c-7725
|
2023-01-10T22:28:19Z
|
2023-01-10T22:28:19Z
| null |
['CVE-2023-22489']
|
Any Flarum user including unactivated can reply in public discussions whose first post was permanently deleted
|
If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status.
This includes users that don't have a validated email.
Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This should also be fixed to return the expected 401/403 status.
This happens because when the first post of a discussion is permanently deleted, the `first_post_id` attribute of the discussion becomes `null` which causes access control to be skipped for all new replies.
Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that `discussions.comment_count` is still above zero after the post deletion.
### Impact
This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn't be able to.
In combination with the email notification settings, this could also be used as a way to send unsolicited emails.
Versions between `v1.3.0` and `v1.6.3` are impacted.
### Patches
The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible to v1.6.3 using:
```
composer update --prefer-dist --no-dev -a -W
```
You can then confirm you run the latest version using:
```
composer show flarum/core
```
### Workarounds
If you don't delete the first posts you are not affected. A workaround can be to delete the discussion itself, or amend the database to manually set a `first_post_id`.
### For more information
For any questions or comments on this vulnerability please visit https://discuss.flarum.org/
For support questions create a discussion at https://discuss.flarum.org/t/support.
A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing [security@flarum.org](mailto:security@flarum.org), and we will address it promptly.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'flarum/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.3.0'}, {'fixed': '1.6.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22489'}, {'type': 'WEB', 'url': 'https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015'}, {'type': 'PACKAGE', 'url': 'https://github.com/flarum/framework'}, {'type': 'WEB', 'url': 'https://github.com/flarum/framework/releases/tag/v1.6.3'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T22:28:19Z', 'nvd_published_at': '2023-01-13T19:15:00Z'}
|
1.4.0
|
GHSA-g5qr-xgg7-8q2w
|
2023-02-02T10:31:17Z
|
2023-01-26T21:30:25Z
| null |
['CVE-2022-25350']
|
Command Injection in puppet-facter
|
All versions of the package puppet-facter are vulnerable to Command Injection via the getFact function due to improper input sanitization.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'puppet-facter'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.0.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-25350'}, {'type': 'WEB', 'url': 'https://github.com/olindata/node-puppet-facter/blob/f34bcc754325d71bb3b1b534804e53d6170f15f5/index.js#23L10'}, {'type': 'WEB', 'url': 'https://github.com/olindata/node-puppet-facter/blob/f34bcc754325d71bb3b1b534804e53d6170f15f5/index.js%23L10'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-PUPPETFACTER-3175616'}]
|
{'cwe_ids': ['CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:00:46Z', 'nvd_published_at': '2023-01-26T21:15:00Z'}
|
1.4.0
|
GHSA-7m9r-rq9j-wmmh
|
2023-01-10T00:41:43Z
|
2023-01-10T00:41:43Z
| null |
[]
|
PocketMine-MP vulnerable to denial-of-service by sending large modal form responses
|
### Impact
Due to a workaround for an old client bug (which has since been fixed), very large JSON payloads in `ModalFormResponsePacket` were able to cause the server to spend a significant amount of time processing the packet. Large numbers of these packets were able to hog CPU time so as to prevent the server from processing other connections in a timely manner.
### Patches
The problem has been addressed in 3baa5ab71214f96e6e7ab12cb9beef08118473b5 by removing the workaround code.
### Workarounds
Plugins could cancel `DataPacketReceiveEvent` for this packet, decode the data their way, and then call `Player->onFormSubmit()` directly, bypassing the vulnerable code.
|
[{'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': 'Packagist', 'name': 'pocketmine/pocketmine-mp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.12.5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pmmp/PocketMine-MP/security/advisories/GHSA-7m9r-rq9j-wmmh'}, {'type': 'PACKAGE', 'url': 'https://github.com/pmmp/PocketMine-MP'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T00:41:43Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-33gv-rvgq-gpxp
|
2023-02-04T00:30:29Z
|
2023-01-27T00:30:18Z
| null |
['CVE-2023-0493']
|
HTML injections in BTCPayServer
|
Improper Neutralization of Equivalent Special Elements in GitHub repository btcpayserver/btcpayserver prior to 1.7.5.
|
[{'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': 'NuGet', 'name': 'BTCPayServer.Client'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.7.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0493'}, {'type': 'WEB', 'url': 'https://github.com/btcpayserver/btcpayserver/commit/02070d65836cd24627929b3403efbae8de56039a'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/3a73b45c-6f3e-4536-a327-cdfdbc59896f'}, {'type': 'WEB', 'url': 'http://packetstormsecurity.com/files/171732/BTCPay-Server-1.7.4-HTML-Injection.html'}]
|
{'cwe_ids': ['CWE-76'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-02-04T00:30:29Z', 'nvd_published_at': '2023-01-26T23:15:00Z'}
|
1.4.0
|
GHSA-5xhh-6xfv-7q42
|
2023-02-03T20:33:43Z
|
2023-01-26T21:30:17Z
| null |
['CVE-2023-24458']
|
Cross-site request forgery vulnerability in Jenkins BearyChat Plugin
|
A cross-site request forgery (CSRF) vulnerability in Jenkins BearyChat Plugin 3.0.2 and earlier allows attackers to connect to an attacker-specified URL.
|
[{'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.plugins:bearychat'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '3.0.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24458'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2745'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T00:55:48Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-h452-7996-h45h
|
2023-01-23T16:59:52Z
|
2023-01-18T06:31:03Z
| null |
['CVE-2022-25901']
|
cookiejar Regular Expression Denial of Service via Cookie.parse function
|
Versions of the package cookiejar before 2.1.4 are vulnerable to Regular Expression Denial of Service (ReDoS) via the `Cookie.parse` function and other aspects of the API, which use an insecure regular expression for parsing cookie values. Applications could be stalled for extended periods of time if untrusted input is passed to cookie values or attempted to parse from request headers.
Proof of concept:
```
ts\nconst { CookieJar } = require("cookiejar");
const jar = new CookieJar();
const start = performance.now();
const attack = "a" + "t".repeat(50_000);
jar.setCookie(attack);
console.log(`CookieJar.setCookie(): ${performance.now() - start}ms`);
```
```
CookieJar.setCookie(): 2963.214399999939ms
```
|
[{'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': 'cookiejar'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.1.4'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.webjars.npm:cookiejar'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '2.1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-25901'}, {'type': 'WEB', 'url': 'https://github.com/bmeck/node-cookiejar/pull/39'}, {'type': 'WEB', 'url': 'https://github.com/bmeck/node-cookiejar/pull/39/commits/eaa00021caf6ae09449dde826108153b578348e5'}, {'type': 'PACKAGE', 'url': 'https://github.com/bmeck/node-cookiejar'}, {'type': 'WEB', 'url': 'https://github.com/bmeck/node-cookiejar/blob/master/cookiejar.js#23L73'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-3176681'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-COOKIEJAR-3149984'}]
|
{'cwe_ids': ['CWE-1333'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-23T16:59:52Z', 'nvd_published_at': '2023-01-18T05:15:00Z'}
|
1.4.0
|
GHSA-qjm7-55vv-3c5f
|
2023-01-20T23:35:16Z
|
2023-01-18T03:31:17Z
| null |
['CVE-2018-25077']
|
mel-spintax has Inefficient Regular Expression Complexity
|
A vulnerability was found in melnaron mel-spintax. It has been rated as problematic. Affected by this issue is some unknown functionality of the file `lib/spintax.js`. The manipulation of the argument text leads to inefficient regular expression complexity. The name of the patch is 37767617846e27b87b63004e30216e8f919637d3. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-218456.
|
[]
|
[{'package': {'ecosystem': 'npm', 'name': 'mel-spintax'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-25077'}, {'type': 'WEB', 'url': 'https://github.com/melnaron/mel-spintax/commit/37767617846e27b87b63004e30216e8f919637d3'}, {'type': 'PACKAGE', 'url': 'https://github.com/melnaron/mel-spintax'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.218456'}]
|
{'cwe_ids': ['CWE-1333'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:35:16Z', 'nvd_published_at': '2023-01-18T01:15:00Z'}
|
1.4.0
|
GHSA-h8p8-6378-649p
|
2023-02-06T16:41:27Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24430']
|
XML external entity reference vulnerability on agents in Jenkins Semantic Versioning Plugin
|
Jenkins Semantic Versioning Plugin 1.14 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
|
[{'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': 'Maven', 'name': 'org.jenkins-ci.plugins:semantic-versioning-plugin'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.15'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24430'}, {'type': 'WEB', 'url': 'https://github.com/jenkinsci/semantic-versioning-plugin/commit/8df2fabd7d7396ae29c374914d1357744d3e454f'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2973%20(2)'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:16:23Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-3fwq-qv5v-2wxf
|
2023-01-25T22:03:31Z
|
2023-01-18T03:31:17Z
| null |
['CVE-2020-36651']
|
Path Traversal in web-node-server
|
A vulnerability has been found in youngerheart nodeserver and classified as critical. Affected by this vulnerability is an unknown functionality of the file nodeserver.js. The manipulation leads to path traversal. The name of the patch is c4c0f0138ab5afbac58e03915d446680421bde28. It is recommended to apply a patch to fix this issue. The identifier VDB-218461 was assigned to this vulnerability.
|
[{'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': 'web-node-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.0.11'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36651'}, {'type': 'WEB', 'url': 'https://github.com/youngerheart/nodeserver/pull/6'}, {'type': 'WEB', 'url': 'https://github.com/youngerheart/nodeserver/commit/c4c0f0138ab5afbac58e03915d446680421bde28'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.218461'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.218461'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-25T22:03:31Z', 'nvd_published_at': '2023-01-18T01:15:00Z'}
|
1.4.0
|
GHSA-6w89-c65w-jx2c
|
2023-01-26T19:05:38Z
|
2023-01-19T18:30:21Z
| null |
['CVE-2022-47105']
|
Jeecg-boot is vulnerable to SQL injection
|
Jeecg-boot v3.4.4 was discovered to contain a SQL injection vulnerability via the component `/sys/dict/queryTableData`. A patch was released in commit 0fc374.
|
[{'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': 'Maven', 'name': 'org.jeecgframework.boot:jeecg-boot-base-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '3.4.4'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.jeecgframework.boot:jeecg-module-system'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '3.4.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-47105'}, {'type': 'WEB', 'url': 'https://github.com/jeecgboot/jeecg-boot/issues/4393'}, {'type': 'WEB', 'url': 'https://github.com/jeecgboot/jeecg-boot/commit/0fc374de4745eac52620eeb8caf6a7b76127529a'}, {'type': 'PACKAGE', 'url': 'https://github.com/jeecgboot/jeecg-boot'}]
|
{'cwe_ids': ['CWE-89'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:08:23Z', 'nvd_published_at': '2023-01-19T16:15:00Z'}
|
1.4.0
|
GHSA-x477-fq37-q5wr
|
2023-01-27T00:55:27Z
|
2023-01-27T00:55:27Z
| null |
[]
|
Initial debug-host handler implementation could leak information and facilitate denial of service
|
### Impact
version 1.5.0 and 1.6.0 when using the new `debug-host` feature could expose unnecessary information about the host
### Patches
Use 1.6.1 or newer
### Workarounds
Downgrade to 1.4.0 or set `debug-host` to empty
### References
https://github.com/fortio/proxy/pull/38
Q&A https://github.com/fortio/proxy/discussions
|
[]
|
[{'package': {'ecosystem': 'Go', 'name': 'fortio.org/proxy'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.5.0'}, {'fixed': '1.6.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/fortio/proxy/security/advisories/GHSA-x477-fq37-q5wr'}, {'type': 'WEB', 'url': 'https://github.com/fortio/proxy/pull/38'}, {'type': 'PACKAGE', 'url': 'https://github.com/fortio/proxy'}]
|
{'cwe_ids': ['CWE-200'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T00:55:27Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-36fh-84j7-cv5h
|
2023-03-03T23:25:11Z
|
2023-01-29T06:30:52Z
| null |
['CVE-2022-48285']
|
JSZip contains Path Traversal via loadAsync
|
loadAsync in JSZip before 3.8.0 allows Directory Traversal via a crafted ZIP archive.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'jszip'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.8.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-48285'}, {'type': 'WEB', 'url': 'https://github.com/Stuk/jszip/commit/2edab366119c9ee948357c02f1206c28566cdf15'}, {'type': 'WEB', 'url': 'https://exchange.xforce.ibmcloud.com/vulnerabilities/244499'}, {'type': 'PACKAGE', 'url': 'https://github.com/Stuk/jszip'}, {'type': 'WEB', 'url': 'https://github.com/Stuk/jszip/compare/v3.7.1...v3.8.0'}, {'type': 'WEB', 'url': 'https://www.mend.io/vulnerability-database/WS-2023-0004'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-02-01T18:08:04Z', 'nvd_published_at': '2023-01-29T05:15:00Z'}
|
1.4.0
|
GHSA-5g2h-9x5v-5h3x
|
2023-04-06T22:57:41Z
|
2023-01-10T06:30:25Z
| null |
['CVE-2021-46871']
|
phoenix_html allows Cross-site Scripting in HEEx class attributes
|
tag.ex in Phoenix Phoenix.HTML (aka phoenix_html) before 3.0.4 allows XSS in HEEx class attributes
|
[{'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': 'phoenix_html'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.0.4'}]}]}, {'package': {'ecosystem': 'Hex', 'name': 'phoenix_html'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.0.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-46871'}, {'type': 'WEB', 'url': 'https://github.com/phoenixframework/phoenix_html/commit/62a0139fb716bcdce697f6221244bd81d321d620'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-j3gg-r6gp-95q2'}, {'type': 'PACKAGE', 'url': 'https://github.com/phoenixframework/phoenix_html/'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T22:16:31Z', 'nvd_published_at': '2023-01-10T06:15:00Z'}
|
1.4.0
|
GHSA-939x-6mwj-96r2
|
2023-02-04T00:30:33Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24426']
|
Insufficient Session Expiration in Jenkins Azure AD Plugin
|
Jenkins Azure AD Plugin 303.va_91ef20ee49f and earlier does not invalidate the previous session on login.
|
[{'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.plugins:azure-ad'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '303.va'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24426'}, {'type': 'PACKAGE', 'url': 'https://github.com/jenkinsci/azure-ad-plugin'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2980'}]
|
{'cwe_ids': ['CWE-613'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-02-04T00:30:33Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-93cw-f5jj-x85w
|
2023-01-25T18:04:00Z
|
2023-01-17T23:58:06Z
| null |
['CVE-2023-22731']
|
Shopware vulnerable to Improper Control of Generation of Code in Twig rendered views
|
### Impact
In Twig environment **without the Sandbox extension**, it is possible to refer to PHP functions in twig filters like `map`, `filter`, `sort`. This allows in the template to call any global PHP function.
### Patches
The problem has been fixed with 6.4.18.1 with an override of the specified filters until the integration of the Sandbox extension has been finished.
### Workarounds
For older versions of 6.1, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
### References
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-01-2023?category=security-updates
|
[{'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': 'shopware/platform'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.18.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.18.0'}}, {'package': {'ecosystem': 'Packagist', 'name': 'shopware/core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.4.18.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 6.4.18.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/shopware/platform/security/advisories/GHSA-93cw-f5jj-x85w'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22731'}, {'type': 'WEB', 'url': 'https://github.com/shopware/platform/commit/89d1ea154689cb6202e0d3a0ceeae0febb0c09e1'}, {'type': 'WEB', 'url': 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-01-2023?category=security-updates'}, {'type': 'PACKAGE', 'url': 'https://github.com/shopware/platform'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-17T23:58:06Z', 'nvd_published_at': '2023-01-17T22:15:00Z'}
|
1.4.0
|
GHSA-rh3m-pr36-xh2f
|
2023-01-12T23:43:29Z
|
2023-01-07T21:30:38Z
| null |
['CVE-2015-10029']
|
kelvinmo simplexrd vulnerable to Improper Restriction of XML External Entity Reference
|
A vulnerability classified as problematic was found in kelvinmo simplexrd up to 3.1.0. This vulnerability affects unknown code of the file `simplexrd/simplexrd.class.php`. The manipulation leads to xml external entity reference. Upgrading to version 3.1.1 is able to address this issue. The name of the patch is 4c9f2e028523ed705b555eca2c18c64e71f1a35d. It is recommended to upgrade the affected component. VDB-217630 is the identifier assigned to this vulnerability.
|
[{'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': 'kelvinmo/simplexrd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2015-10029'}, {'type': 'WEB', 'url': 'https://github.com/kelvinmo/simplexrd/commit/4c9f2e028523ed705b555eca2c18c64e71f1a35d'}, {'type': 'PACKAGE', 'url': 'https://github.com/kelvinmo/simplexrd'}, {'type': 'WEB', 'url': 'https://github.com/kelvinmo/simplexrd/releases/tag/v3.1.1'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.217630'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.217630'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-12T23:43:29Z', 'nvd_published_at': '2023-01-07T20:15:00Z'}
|
1.4.0
|
GHSA-746g-3gfp-hfhw
|
2023-09-05T21:57:50Z
|
2023-01-26T23:54:07Z
| null |
['CVE-2015-8314']
|
Devise Gem for Ruby Unauthorized Access Using "Remember Me" Cookie
|
Devise version before 3.5.4 uses cookies to implement a "Remember me" functionality. However, it generates the same cookie for all devices. If an attacker manages to steal a remember me cookie and the user does not change the password frequently, the cookie can be used to gain access to the application indefinitely.
|
[]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'devise'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.5.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/heartcombo/devise/commit/c92996646aba2d25b2c3e235fe0c4f1a84b70d24'}, {'type': 'PACKAGE', 'url': 'https://github.com/heartcombo/devise'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/devise/CVE-2015-8314.yml'}, {'type': 'WEB', 'url': 'http://blog.plataformatec.com.br/2016/01/improve-remember-me-cookie-expiration-in-devise/'}]
|
{'cwe_ids': ['CWE-288'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-26T23:54:07Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gmhf-37fx-c4q8
|
2023-02-03T20:40:11Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24433']
|
Missing permission checks in Jenkins Orka Plugin allow capturing credentials
|
Missing permission checks in Jenkins Orka by MacStadium Plugin 1.31 and earlier allow attackers with Overall/Read permission to connect to an attacker-specified HTTP server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'io.jenkins.plugins:macstadium-orka'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.32'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24433'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2772%20(2)'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:26:34Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-98qc-v8vg-mcx4
|
2023-02-03T20:35:16Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24454']
|
Plaintext Storage of a Password in Jenkins TestQuality Updater Plugin
|
Jenkins TestQuality Updater Plugin 1.3 and earlier stores the TestQuality Updater password unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.plugins:testquality-updater'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24454'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2091'}]
|
{'cwe_ids': ['CWE-256', 'CWE-312'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T00:58:21Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-3244-8mff-w398
|
2023-01-10T22:48:43Z
|
2023-01-10T22:48:43Z
| null |
[]
|
Reflected XSS in Gotify's /docs via import of outdated Swagger UI
|
### Impact
Gotify exposes an outdated instance of the [Swagger UI](https://swagger.io/tools/swagger-ui/) API documentation frontend at `/docs` which is susceptible to reflected XSS attacks when loading external Swagger config files.
Specifically, the DOMPurify version included with this version of Swagger UI is vulnerable to a [rendering XSS](https://www.vidocsecurity.com/blog/hacking-swagger-ui-from-xss-to-account-takeovers/) incorporating the mutation payload detailed in [CVE-2020-26870](https://research.securitum.com/mutation-xss-via-mathml-mutation-dompurify-2-0-17-bypass/) which was patched in 2021. This is further tracked in the GitHub Advisory Database as GHSA-QRMM-W75W-3WPX.
An attacker can execute arbitrary JavaScript and potentially take over the account of the user that clicked the link. Keep in mind, the Gotify UI won't natively expose such a malicious link, so an attacker has to get the user to open the malicious link in a context outside of Gotify.
### Patches
The vulnerability has been fixed in version 2.2.3.
### References
https://github.com/gotify/server/pull/541
|
[]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/gotify/server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.2.3'}]}], 'database_specific': {'last_known_affected_version_range': '<= 2.2.2'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/gotify/server/security/advisories/GHSA-3244-8mff-w398'}, {'type': 'WEB', 'url': 'https://github.com/gotify/server/pull/541'}, {'type': 'PACKAGE', 'url': 'https://github.com/gotify/server'}, {'type': 'WEB', 'url': 'https://research.securitum.com/mutation-xss-via-mathml-mutation-dompurify-2-0-17-bypass/'}, {'type': 'WEB', 'url': 'https://www.vidocsecurity.com/blog/hacking-swagger-ui-from-xss-to-account-takeovers/'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T22:48:43Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-hj4g-4w36-x8hp
|
2023-01-27T21:42:18Z
|
2023-01-20T18:30:22Z
| null |
['CVE-2022-47747']
|
Kraken has arbitrary file read vulnerability via component testfs
|
kraken <= 0.1.4 has an arbitrary file read vulnerability via the component `testfs`.
|
[{'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': 'Go', 'name': 'github.com/uber/kraken'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.1.4'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-47747'}, {'type': 'WEB', 'url': 'https://github.com/uber/kraken/issues/333'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-hj4g-4w36-x8hp'}, {'type': 'PACKAGE', 'url': 'https://github.com/uber/kraken'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T21:56:09Z', 'nvd_published_at': '2023-01-20T17:15:00Z'}
|
1.4.0
|
GHSA-pfpr-3463-c6jh
|
2023-01-24T23:28:35Z
|
2023-01-09T21:55:14Z
| null |
['CVE-2022-46648']
|
ruby-git has potential remote code execution vulnerability
|
The git gem, between versions 1.2.0 and 1.12.0, incorrectly parsed the output of the `git ls-files` command using `eval()` to unescape quoted file names. If a file name was added to the git repository contained special characters, such as `\n`, then the `git ls-files` command would print the file name in quotes and escape any special characters. If the `Git#ls_files` method encountered a quoted file name it would use `eval()` to unquote and unescape any special characters, leading to potential remote code execution. Version 1.13.0 of the git gem was released which correctly parses any quoted file names.
|
[{'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': 'RubyGems', 'name': 'git'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.2.0'}, {'fixed': '1.13.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-46648'}, {'type': 'WEB', 'url': 'https://github.com/ruby-git/ruby-git/pull/602'}, {'type': 'PACKAGE', 'url': 'https://github.com/ruby-git/ruby-git'}, {'type': 'WEB', 'url': 'https://github.com/ruby-git/ruby-git/releases/tag/v1.13.0'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/git/CVE-2022-46648.yml'}, {'type': 'WEB', 'url': 'https://jvn.jp/en/jp/JVN16765254/index.html'}, {'type': 'WEB', 'url': 'https://lists.debian.org/debian-lts-announce/2023/01/msg00043.html'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-09T21:55:14Z', 'nvd_published_at': '2023-01-17T10:15:00Z'}
|
1.4.0
|
GHSA-c45c-39f6-6gw9
|
2023-01-25T19:38:13Z
|
2023-01-25T19:38:13Z
| null |
[]
|
Rancher generated tokens not revoked after modifications made to authentication provider
|
### Impact
This issue affects Rancher versions from 2.5.0 up to and including 2.5.16, from 2.6.0 up to and including 2.6.9 and 2.7.0. It only affects Rancher setups that have an external [authentication provider](https://ranchermanager.docs.rancher.com/pages-for-subheaders/authentication-config) configured or had one configured in the past.
It was discovered that when an external authentication provider is configured in Rancher and then disabled, the Rancher generated [tokens](https://ranchermanager.docs.rancher.com/reference-guides/about-the-api/api-tokens) associated with users who had access granted through the now disabled auth provider are not revoked. This allows users to retain access to Rancher and `kubectl` access to clusters managed by Rancher, according to their previous configured permissions, even after they are supposed to have lost it due to the auth provider been disabled.
The problem also occurs if the auth provider is configured (and is still enabled) to use the [access level scopes](https://ranchermanager.docs.rancher.com/pages-for-subheaders/authentication-config) `allow members of clusters and projects, plus authorized users & groups` and `restrict access to only the authorized users & groups`. In this case, removing users and groups from the authorized lists will not revoke the access tokens and they will remain valid.
An example scenario is:
1. OpenLDAP, MS Active Directory (AD) or any other external [authentication provider](https://ranchermanager.docs.rancher.com/pages-for-subheaders/authentication-config) is configured as an auth provider.
2. A user (`cluster-owner`) is granted `cluster-owner` permissions on a downstream cluster (`test-cluster`).
3. `cluster-owner` logs in using their external auth provider username and password.
4. `cluster-owner` generates a `kubeconfig` token for `test-cluster`.
5. The configured external auth provider is disabled.
In this scenario, the `kubeconfig` generated in step 4 will still be valid after step 5, and `test-cluster` can still be accessed using the `kubeconfig` token.
By default, tokens for authenticated session have their `ttl` (time to live) set to `960` minutes, so they will expire after `16` hours. `kubeconfig` tokens are configured to never expire, and their `ttl` is set to `0`. These configurations can be changed in the Rancher's settings (`Configuration > Global Settings > Settings`) with the [parameters](https://ranchermanager.docs.rancher.com/reference-guides/about-the-api/api-tokens) `auth-user-session-ttl-minutes` and `kubeconfig-default-token-ttl-minutes`, respectively.
### Workarounds
If you cannot update to a patched Rancher version, the recommended workaround is to review and remove tokens associated with auth providers manually.
The tokens can be reviewed by executing `kubectl get tokens` in Rancher's `local` cluster. Each found token must be manually reviewed to check if it belongs to a user from a disabled auth provider or a user who's access was previously removed from the auth provider (when the auth provider is still enabled and is or was configured to use access level scopes, as mentioned above). The identified tokens can be removed with `kubectl delete tokens <token_name>`.
It is important to mention that this workaround must be done every time an auth provider is disabled in case you cannot update to a patched version.
### Patches
Patched versions include releases 2.5.17, 2.6.10, 2.7.1 and later versions. After updating to a patched version, it is highly recommended to review the existing tokens and remove tokens related to disabled auth providers as described above in the workaround section.
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify 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:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rancher'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.17'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rancher'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.10'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rancher'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.7.0'}, {'fixed': '2.7.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rancher/rancher/security/advisories/GHSA-c45c-39f6-6gw9'}, {'type': 'PACKAGE', 'url': 'https://github.com/rancher/rancher'}]
|
{'cwe_ids': ['CWE-287'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-25T19:38:13Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xwhj-pqcg-8rcr
|
2023-01-20T23:35:17Z
|
2023-01-20T23:35:17Z
| null |
[]
|
CakePHP vulnerable to Cross-site Scripting in some development error pages
|
CakePHP 3.4 prior to 3.4.14, 3.5 prior to 3.5.17, and 3.6 prior to 3.6.4 contains a cross-site-scripting (XSS) vulnerability in the development only `missing route` and `duplicate named route` error pages.
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.4.0'}, {'fixed': '3.4.14'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.5.0'}, {'fixed': '3.5.17'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'cakephp/cakephp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.6.0'}, {'fixed': '3.6.4'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/cakephp/cakephp/commit/1ea0c87de729e0dcd53eb6fe3bc86ba739121d8e'}, {'type': 'WEB', 'url': 'https://bakery.cakephp.org/2018/05/20/cakephp_364_3517_3414_released.html'}, {'type': 'WEB', 'url': 'https://github.com/FriendsOfPHP/security-advisories/blob/master/cakephp/cakephp/2018-05-20.yaml'}, {'type': 'PACKAGE', 'url': 'https://github.com/cakephp/cakephp'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:35:17Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-crhg-xgrg-vvcc
|
2023-01-13T21:34:29Z
|
2023-01-13T21:34:29Z
| null |
[]
|
a12nserver vulnerable to potential SQL Injections via Knex dependency
|
### Impact
Users of a12nserver that use MySQL might be vulnerable to SQL injection bugs.
If you use a12nserver and MySQL, update as soon as possible. This SQL injection bug might let an attacker obtain OAuth2 Access Tokens for users unrelated to those that permitted OAuth2 clients.
### Patches
The knex dependency has been updated to 2.4.0 in a12nserver 0.23.0
### Workarounds
No further workarounds
### References
* https://github.com/knex/knex/issues/1227
* https://nvd.nist.gov/vuln/detail/CVE-2016-20018
* https://www.ghostccamm.com/blog/knex_sqli/
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': '@curveball/a12n-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.20.0'}, {'fixed': '0.23.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/curveball/a12n-server/security/advisories/GHSA-crhg-xgrg-vvcc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2016-20018'}, {'type': 'WEB', 'url': 'https://github.com/knex/knex/issues/1227'}, {'type': 'WEB', 'url': 'https://github.com/curveball/a12n-server/commit/f4acd7549043e6e2b8917b77a50dce0756a922cc'}, {'type': 'PACKAGE', 'url': 'https://github.com/curveball/a12n-server'}, {'type': 'WEB', 'url': 'https://github.com/curveball/a12n-server/releases/tag/v0.23.0'}, {'type': 'WEB', 'url': 'https://www.ghostccamm.com/blog/knex_sqli/'}]
|
{'cwe_ids': ['CWE-89'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-13T21:34:29Z', 'nvd_published_at': '2023-01-13T16:15:00Z'}
|
1.4.0
|
GHSA-rv9x-wmw4-44qj
|
2023-01-20T16:54:17Z
|
2023-01-12T03:30:15Z
| null |
['CVE-2023-0227']
|
Pyload Insufficient Session Expiration vulnerability
|
Pyload 0.5.0b3.dev35 has an Insufficient Session Expiration vulnerability. A patch is available and anticipated to be part of version 0.5.0b3.dev36.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'pyload-ng'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.0b3.dev36'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.5.0b3.dev35'}}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0227'}, {'type': 'WEB', 'url': 'https://github.com/pyload/pyload/commit/c035714c0596b704b11af0f8a669352f128ad2d9'}, {'type': 'PACKAGE', 'url': 'https://github.com/pyload/pyload'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/af3101d7-fea6-463a-b7e4-a48be219e31b'}]
|
{'cwe_ids': ['CWE-613'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-12T20:54:01Z', 'nvd_published_at': '2023-01-12T01:15:00Z'}
|
1.4.0
|
GHSA-q95h-cqrv-8jv5
|
2023-01-20T19:33:40Z
|
2023-01-20T19:33:40Z
| null |
[]
|
ExifTool vulnerable to arbitrary code execution
|
### Impact
Arbitrary code execution can occur when running `exiftool` against files with hostile metadata payloads
### Patches
ExifTool has already been patched in version 12.24. `exiftool_vendored.rb`, which vendors ExifTool, includes this patch in [v12.25.0](https://github.com/exiftool-rb/exiftool_vendored.rb/releases/tag/v12.25.0).
### Workarounds
No
### References
https://twitter.com/wcbowling/status/1385803927321415687
https://nvd.nist.gov/vuln/detail/CVE-2021-22204
### For more information
If you have any questions or comments about this advisory:
Open an issue in [exiftool_vendored.rb](https://github.com/exiftool-rb/exiftool_vendored.rb/issues)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'exiftool_vendored'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '12.25.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/exiftool-rb/exiftool_vendored.rb/security/advisories/GHSA-q95h-cqrv-8jv5'}, {'type': 'PACKAGE', 'url': 'https://github.com/exiftool-rb/exiftool_vendored.rb'}, {'type': 'WEB', 'url': 'https://twitter.com/wcbowling/status/1385803927321415687'}]
|
{'cwe_ids': ['CWE-74'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T19:33:40Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-fcg4-pm6h-9xx2
|
2023-01-24T18:53:55Z
|
2023-01-16T12:30:17Z
| null |
['CVE-2022-43721']
|
Apache Superset Open Redirect vulnerability
|
An authenticated attacker with update datasets permission could change a dataset link to an untrusted site, users could be redirected to this site when clicking on that specific dataset. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.
|
[{'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': 'PyPI', 'name': 'apache-superset'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'apache-superset'}, 'versions': ['2.0.0']}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-43721'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/superset'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/s6sqt5jmcv6qxtvdot1t5tpt57v439kg'}]
|
{'cwe_ids': ['CWE-601'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T16:24:43Z', 'nvd_published_at': '2023-01-16T11:15:00Z'}
|
1.4.0
|
GHSA-x73w-g8hx-v7rp
|
2023-01-28T01:18:11Z
|
2023-01-20T21:30:32Z
| null |
['CVE-2020-23256']
|
Code injection in electerm
|
An issue was discovered in Electerm 1.3.22, allows attackers to execute arbitrary code via unverified request to electerms service.
|
[{'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': 'electerm'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.3.22'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-23256'}, {'type': 'WEB', 'url': 'https://github.com/electerm/electerm/issues/1686'}, {'type': 'PACKAGE', 'url': 'https://github.com/electerm/electerm'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-28T01:18:11Z', 'nvd_published_at': '2023-01-20T19:15:00Z'}
|
1.4.0
|
GHSA-77cc-w3wm-6whp
|
2023-01-12T23:42:07Z
|
2023-01-06T12:31:34Z
| null |
['CVE-2016-15011']
|
dssp vulnerable to Improper Restriction of XML External Entity Reference
|
A vulnerability classified as problematic was found in e-Contract dssp up to 1.3.1. Affected by this vulnerability is the function `checkSignResponse` of the file `dssp-client/src/main/java/be/e_contract/dssp/client/SignResponseVerifier.java`. The manipulation leads to xml external entity reference. Upgrading to version 1.3.2 can address this issue. The name of the patch is ec4238349691ec66dd30b416ec6eaab02d722302. It is recommended to upgrade the affected component. The identifier VDB-217549 was assigned to this vulnerability.
|
[{'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': 'Maven', 'name': 'be.e_contract.dssp:dssp-client'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.3.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2016-15011'}, {'type': 'WEB', 'url': 'https://github.com/e-Contract/dssp/commit/ec4238349691ec66dd30b416ec6eaab02d722302'}, {'type': 'PACKAGE', 'url': 'https://github.com/e-Contract/dssp'}, {'type': 'WEB', 'url': 'https://github.com/e-Contract/dssp/releases/tag/dssp-1.3.2'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.217549'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.217549'}]
|
{'cwe_ids': ['CWE-611'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-12T23:42:07Z', 'nvd_published_at': '2023-01-06T10:15:00Z'}
|
1.4.0
|
GHSA-hm7f-rq7q-j9xp
|
2023-01-26T17:04:28Z
|
2023-01-20T03:30:28Z
| null |
['CVE-2023-0410']
|
@builder.io/qwik vulnerable to Cross-site Scripting
|
@builder.io/qwik prior to version 0.16.2 is vulnerable to cross-site scripting due to attribute names and the class attribute values not being properly handled.
|
[{'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': '@builder.io/qwik'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.16.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0410'}, {'type': 'WEB', 'url': 'https://github.com/builderio/qwik/commit/4b2f89dbbd2bc0a2c92eae1a49bdd186e589151a'}, {'type': 'PACKAGE', 'url': 'https://github.com/BuilderIO/qwik'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/2da583f0-7f66-4ba7-9bed-8e7229aa578e'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:00:55Z', 'nvd_published_at': '2023-01-20T01:15:00Z'}
|
1.4.0
|
GHSA-8f5j-mgx9-5hm5
|
2023-01-24T18:53:57Z
|
2023-01-16T12:30:17Z
| null |
['CVE-2022-45438']
|
Apache Superset has Improper Access Control
|
When explicitly enabling the feature flag `DASHBOARD_CACHE` (disabled by default), the system allowed for an unauthenticated user to access dashboard configuration metadata using a REST API Get endpoint. This issue affects Apache Superset version 1.5.2 and prior versions and version 2.0.0.
|
[{'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': 'apache-superset'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.5.2'}]}]}, {'package': {'ecosystem': 'PyPI', 'name': 'apache-superset'}, 'versions': ['2.0.0']}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-45438'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/superset'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/snxbkf2x9kww7s0wkmydct9nhqqn9rv9'}]
|
{'cwe_ids': ['CWE-284', 'CWE-668'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:15:47Z', 'nvd_published_at': '2023-01-16T11:15:00Z'}
|
1.4.0
|
GHSA-7m72-mh5r-6j3r
|
2023-02-15T22:01:37Z
|
2023-01-25T19:35:02Z
| null |
['CVE-2022-43759']
|
Privilege escalation in project role template binding (PRTB) and -promoted roles
|
### Impact
An issue was discovered in Rancher versions from 2.5.0 up to and including 2.5.16 and from 2.6.0 up to and including 2.6.9, where an authorization logic flaw allows privilege escalation via project role template binding (PRTB) and `-promoted` roles. This issue is not present in Rancher 2.7 releases.
Note: Consult Rancher [documentation](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/authentication-permissions-and-global-configuration/manage-role-based-access-control-rbac/cluster-and-project-roles) for more information about cluster and project roles and [KB 000020097](https://www.suse.com/support/kb/doc/?id=000020097) for information about `-promoted` roles.
This privilege escalation is possible for users with access to the `escalate` verb on PRTBs (`projectroletemplatebindings.management.cattle.io`), including users with `*` verbs on PRTBs (see notes below for more information). These users can escalate permissions for any `-promoted` resource (see the table below for a full enumeration) in any cluster where they have a PRTB granting such permissions in at least one project in the cluster.
On a default Rancher setup, only the following roles have such permissions:
1. Project Owner
2. Manage Project Members
These roles have permissions to affect the following resources:
| Resource | API Group | Affected Rancher version |
| - | - | - |
| navlinks | ui.cattle.io | 2.6 |
| nodes | "" | 2.6 |
| persistentvolumes | "" | 2.5, 2.6 |
| persistentvolumes | core | 2.5, 2.6 |
| storageclasses | storage.k8s.io | 2.5, 2.6 |
| apiservices | apiregistration.k8s.io | 2.5, 2.6 |
| clusterrepos | catalog.cattle.io | 2.5, 2.6 |
| clusters (`local` only) | management.cattle.io | 2.5, 2.6 |
Notes:
1. During the calculation of the CVSS score, `privileges required` was considered as `high` because, by default, `standard user` and `user-base` users in Rancher do not have `create`, `patch` and `update` permissions on `roletemplates`.
2. If a role template with access to those objects was already created by another user in the cluster, then this issue can be exploited by users without the mentioned permissions from point 1.
### Workarounds
If updating Rancher to a patched version is not possible, then the following workarounds must be observed to mitigate this issue:
1. Only grant Project Owner and Manage Project Members roles to trusted users.
5. Minimize the creation of custom roles that contain the `escalate`, `*` or write verbs (`create`, `delete`, `patch`, `update`) on `projectroletemplatebindings` resource, and only grant such custom roles to trusted users.
6. Minimize the number of users that have permissions to `create`, `patch` and `update` `roletemplates`.
### Patches
Patched versions include releases 2.5.17 and 2.6.10 and later versions. This issue is not present in Rancher 2.7 releases.
### Detection
The following script was developed to list role template bindings that give written access to the affected resources listed above. It is highly recommended to run the script in your environment and review the list of identified roles and role template bindings for possible signs of exploitation of this issue. The script requires `jq` installed and a `kubeconfig` with access to Rancher local cluster; it can also be executed in Rancher's kubectl shell.
```shell
#!/bin/bash
help="
Usage: bash find_promoted_resource.sh \n \n
Requires: \n
- jq installed and on path \n
- A kubeconfig pointing at rancher's local cluster (can also run from rancher's kubectl shell) \n \n
Outputs a list of roletemplates and roletemplate bindings which give write access to promoted resources.
"
if [[ $1 == "-h" || $1 == "--help" ]]
then
echo -e $help
exit 0
fi
# first, get the current roletemplates so that we only issue a get once
kubectl get roletemplates.management.cattle.io -o json >> script_templates.json
# find roles which have write access to a promoted resource. Filter on roleTemplates which fulfill all requirements:
# Have a project context
# Have some rules
# Have one/more of the target api groups, or a * in the api groups
# Have one/more of the target resources, or a * in the resources
# Have a verb that is not read access (i.e. a verb that is not get/list/watch)
roles=$(jq --argjson apiGroups '["", "ui.cattle.io", "core", "storage.k8s.io", "apiregistration.k8s.io", "catalog.cattle.io", "management.cattle.io"]' --argjson resources '["navlinks", "persistentvolumes", "nodes", "storageclasses", "apiservices", "clusterrepos", "clusters"]' --argjson verbs '["get", "list", "watch"]' '.items[] | select(.context=="project" and (.rules | length >= 1)) | select( .rules[] | select( (($apiGroups - .apiGroups | length < 7) or (.apiGroups | index("*"))) and (($resources - .resources | length < 7) or (.resources | index("*"))) and (.verbs - $verbs | length > 0)) | length >= 1 ) | .metadata.name' script_templates.json | jq -s )
# log promoted roles which give direct write access so they can be easily fixed
echo "The following role templates give direct write access to a promoted resource:"
echo $roles
echo -e ""
# find any roles which inherit first-level roles. Mostly a BFS which radiates outward from the known bad roles
old_roles="[]"
new_roles="$roles"
old_length=$(echo $old_roles | jq 'length')
new_length=$(echo $new_roles | jq 'length')
# if our last loop found nothing new, it's safe to stop
while [[ $old_length != $new_length ]];
do
# set old values to what we currently know about
old_roles=$new_roles
old_length=$new_length
# update new values with anything that inherits a "bad" role we know about
new_roles=$(jq --argjson roles "$old_roles" --argjson roleLen "$old_length" '.items[] | .metadata.name as $NAME | select (( $roles | index($NAME)) or ((.roleTemplateNames | length > 0 ) and ($roles - .roleTemplateNames | length < $roleLen))) | .metadata.name ' script_templates.json | jq -s)
new_length=$(echo $new_roles | jq 'length')
done
roles=$new_roles
# log all roles which can give write access, even if it's not first level
echo -e "The following role templates give write access to a promoted resource directly or through inheritance:"
echo $roles
echo -e ""
kubectl get projectroletemplatebindings.management.cattle.io -A -o json >> script_bindings.json
role_template_bindings=$(jq --argjson roleTemplates "$roles" '.items[] | .roleTemplateName as $TemplateName | select($roleTemplates | index($TemplateName)) | .metadata.name' script_bindings.json | jq -s)
# since these bindings could be for users or groups, we need to include all fields which could help identify the subject. But they won't all be present, which makes the list look less pretty
echo -e "The following is a list of bindings which give access to promoted resource, with the format of: bindingName, projectName, userName, userPrincipalName, groupName, groupPrincipalName: "
echo $(jq --argjson bindings "$role_template_bindings" '.items[] | .metadata.name as $BindingName | select ( $bindings | index($BindingName)) | .metadata.name, .projectName, .userName?, .userPrincipalName?, .groupName?, .groupPrincipalName?' script_bindings.json | jq -s)
unset old_roles
unset new_roles
unset roles
unset role_template_bindings
rm script_templates.json
rm script_bindings.json
```
### For more information
If you have any questions or comments about this advisory:
* Reach out to [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.
* Open an issue in [Rancher](https://github.com/rancher/rancher/issues/new/choose) repository.
* Verify 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:H/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rancher'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.17'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/rancher/rancher'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.10'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/rancher/rancher/security/advisories/GHSA-7m72-mh5r-6j3r'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-43759'}, {'type': 'WEB', 'url': 'https://bugzilla.suse.com/show_bug.cgi?id=1205293'}, {'type': 'PACKAGE', 'url': 'https://github.com/rancher/rancher'}]
|
{'cwe_ids': ['CWE-269', 'CWE-284'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-25T19:35:02Z', 'nvd_published_at': '2023-02-07T13:15:00Z'}
|
1.4.0
|
GHSA-vvj3-85vf-fgmw
|
2023-01-20T16:53:40Z
|
2023-01-13T06:30:22Z
| null |
['CVE-2022-21191']
|
global-modules-path Command Injection vulnerability
|
Versions of the package global-modules-path before 3.0.0 are vulnerable to Command Injection due to missing input sanitization or other checks and sandboxes being employed to the getPath function.
|
[{'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': 'global-modules-path'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-21191'}, {'type': 'WEB', 'url': 'https://github.com/rosen-vladimirov/global-modules-path/commit/edbdaff077ea0cf295b1469923c06bbccad3c180'}, {'type': 'WEB', 'url': 'https://github.com/lorenzomigliorero/npm-node-utils/blob/b55dd81c597db657c9751332bb2242403fd3e26b/index.js%23L186'}, {'type': 'PACKAGE', 'url': 'https://github.com/rosen-vladimirov/global-modules-path'}, {'type': 'WEB', 'url': 'https://github.com/rosen-vladimirov/global-modules-path/releases/tag/v3.0.0'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-GLOBALMODULESPATH-3167973'}]
|
{'cwe_ids': ['CWE-77'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-13T21:33:18Z', 'nvd_published_at': '2023-01-13T05:15:00Z'}
|
1.4.0
|
GHSA-w4v5-54p8-m4j5
|
2023-02-02T17:13:25Z
|
2023-01-26T21:30:18Z
| null |
['CVE-2023-24435']
|
Missing permission checks in Jenkins GitHub Pull Request Builder Plugin
|
A missing permission check in Jenkins GitHub Pull Request Builder Plugin 1.42.2 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.plugins:ghprb'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.42.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-24435'}, {'type': 'PACKAGE', 'url': 'https://github.com/jenkinsci/ghprb-plugin'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-01-24/#SECURITY-2789%20(2)'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:20:04Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-vhvq-jh34-3fc8
|
2023-07-18T18:16:45Z
|
2023-01-13T06:30:22Z
|
2023-07-18T18:08:56Z
|
[]
|
Duplicate Advisory: Keycloak allows impersonation and lockout due to email trust not being handled correctly
|
## Duplicate Advisory
This advisory has been withdrawn because it is a duplicate of GHSA-c7xw-p58w-h6fj. This link is maintained to preserve external references.
## Original Description
A flaw was found in Keycloak. This flaw allows impersonation and lockout due to the email trust not being handled correctly in Keycloak. An attacker can shadow other users with the same email and lockout or impersonate them.
|
[{'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': 'Maven', 'name': 'org.keycloak:keycloak-core'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '20.0.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0105'}, {'type': 'WEB', 'url': 'https://access.redhat.com/security/cve/CVE-2023-0105'}, {'type': 'WEB', 'url': 'https://bugzilla.redhat.com/show_bug.cgi?id=2158910'}, {'type': 'PACKAGE', 'url': 'https://github.com/keycloak/keycloak'}]
|
{'cwe_ids': ['CWE-287', 'CWE-841'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-13T21:29:30Z', 'nvd_published_at': '2023-01-13T06:15:00Z'}
|
1.4.0
|
GHSA-5vpv-xmcj-9q85
|
2023-02-07T21:19:19Z
|
2023-01-27T00:54:59Z
| null |
['CVE-2021-41143']
|
Fix for arbitrary file deletion in customer media allows for remote code execution
|
### Impact
Magento admin users with access to the customer media could execute code on the server.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'openmage/magento-lts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '19.4.22'}]}]}, {'package': {'ecosystem': 'Packagist', 'name': 'openmage/magento-lts'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '20.0.0'}, {'fixed': '20.0.19'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-5vpv-xmcj-9q85'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2021-41143'}, {'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/commit/45330ff50439984e806992fa22c3f96c4d660f91'}, {'type': 'PACKAGE', 'url': 'https://github.com/OpenMage/magento-lts'}, {'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/releases/tag/v19.4.22'}, {'type': 'WEB', 'url': 'https://github.com/OpenMage/magento-lts/releases/tag/v20.0.19'}]
|
{'cwe_ids': ['CWE-22', 'CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T00:54:59Z', 'nvd_published_at': '2023-01-27T19:15:00Z'}
|
1.4.0
|
GHSA-g92r-9rxw-cmgx
|
2023-01-23T18:50:12Z
|
2023-01-16T00:30:24Z
| null |
['CVE-2023-0311']
|
phpMyFAQ Improper Authentication vulnerability
|
Improper Authentication in GitHub repository thorsten/phpmyfaq prior to 3.1.10.
|
[{'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': 'thorsten/phpmyfaq'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0311'}, {'type': 'WEB', 'url': 'https://github.com/thorsten/phpmyfaq/commit/fe6e9f02ef1b26a03134b9becda12687ee5f3214'}, {'type': 'PACKAGE', 'url': 'https://github.com/thorsten/phpmyfaq'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/82b0b629-c56b-4651-af3f-17f749751857'}]
|
{'cwe_ids': ['CWE-287'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T22:01:50Z', 'nvd_published_at': '2023-01-15T22:15:00Z'}
|
1.4.0
|
GHSA-v6vp-62vc-84qw
|
2023-01-12T16:48:58Z
|
2023-01-06T12:31:34Z
| null |
['CVE-2022-45935']
|
Apache James server allows an attacker with local access to access private user data in transit
|
Usage of temporary files with insecure permissions by the Apache James server allows an attacker with local access to access private user data in transit. Vulnerable components includes the SMTP stack and IMAP APPEND command. This issue affects Apache James server version 3.7.2 and prior versions.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.james:james-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '3.7.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-45935'}, {'type': 'WEB', 'url': 'https://github.com/apache/james-project/commit/b5580d13d6c74ecbf647127eff1a3ac1086f5493'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/james-project'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/j61fo8xc1rxtofrn8vc33whx35s9cj1d'}]
|
{'cwe_ids': ['CWE-200', 'CWE-319', 'CWE-668'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-09T20:12:10Z', 'nvd_published_at': '2023-01-06T10:15:00Z'}
|
1.4.0
|
GHSA-q9hr-j4rf-8fjc
|
2023-02-07T21:21:41Z
|
2023-01-25T22:02:52Z
| null |
['CVE-2023-22482']
|
JWT audience claim is not verified
|
### Impact
All versions of Argo CD starting with v1.8.2 are vulnerable to an improper authorization bug causing the API to accept certain invalid tokens.
OIDC providers include an `aud` (audience) claim in signed tokens. The value of that claim specifies the intended audience(s) of the token (i.e. the service or services which are meant to accept the token). Argo CD _does_ validate that the token was signed by Argo CD's configured OIDC provider. But Argo CD _does not_ validate the audience claim, so it will accept tokens that are not intended for Argo CD.
If Argo CD's configured OIDC provider also serves other audiences (for example, a file storage service), then Argo CD will accept a token intended for one of those other audiences. Argo CD will grant the user privileges based on the token's `groups` claim, even though those groups were not intended to be used by Argo CD.
This bug also increases the blast radius of a stolen token. If an attacker steals a valid token for a different audience, they can use it to access Argo CD.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.6.0-rc5
* v2.5.8
* v2.4.20
* v2.3.14
The patch introduces a new `allowedAudiences` to the OIDC config block. By default, the client ID is the only allowed audience. Users who _want_ Argo CD to accept tokens intended for a different audience may use `allowedAudiences` to specify those audiences.
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: argocd-cm
data:
oidc.config: |
name: Example
allowedAudiences:
- audience-1
- audience-2
- argocd-client-id # If `allowedAudiences` is non-empty, Argo CD's client ID must be explicitly added if you want to allow it.
``
Even though [the OIDC spec requires the audience claim](https://openid.net/specs/openid-connect-core-1_0.html#IDToken), some tokens may not include it. To avoid a breaking change in a patch release, versions < 2.6.0 of Argo CD will skip the audience claim check for tokens that have no audience. In versions >= 2.6.0, Argo CD will reject all tokens which do not have an audience claim. Users can opt into the old behavior by setting an option:
```yaml
apiVersion: v1
kind: ConfigMap
metadata:
name: argocd-cm
data:
oidc.config: |
name: Example
skipAudienceCheckWhenTokenHasNoAudience: true
```
### Workarounds
There is no workaround besides upgrading.
### Credits
The Argo CD team would like to express their gratitude to Vladimir Pouzanov (@farcaller) from Indeed, who discovered the issue, reported it confidentially according to our [guidelines](https://github.com/argoproj/argo-cd/blob/master/SECURITY.md#reporting-a-vulnerability), and actively worked with the project to provide a remedy. Many thanks to Vladimir!
### References
* [How to configure OIDC in Argo CD](https://argo-cd.readthedocs.io/en/latest/operator-manual/user-management/#existing-oidc-provider)
* [OIDC spec section discussing the audience claim](https://openid.net/specs/openid-connect-core-1_0.html#IDToken)
* [JWT spec section discussing the audience claim](https://www.rfc-editor.org/rfc/rfc7519#section-4.1.3)
### For more information
* Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
* Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-cd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.8.2'}, {'fixed': '2.3.14'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-cd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.4.0'}, {'fixed': '2.4.20'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-cd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.5.0'}, {'fixed': '2.5.8'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/argoproj/argo-cd'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0-rc1'}, {'fixed': '2.6.0-rc5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/argoproj/argo-cd/security/advisories/GHSA-q9hr-j4rf-8fjc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22482'}, {'type': 'PACKAGE', 'url': 'https://github.com/argoproj/argo-cd'}]
|
{'cwe_ids': ['CWE-863'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-25T22:02:52Z', 'nvd_published_at': '2023-01-26T21:18:00Z'}
|
1.4.0
|
GHSA-p33q-4h4m-j994
|
2023-01-12T18:51:20Z
|
2023-01-07T12:30:14Z
| null |
['CVE-2020-36644']
|
Inline SVG vulnerable to Cross-site Scripting
|
A vulnerability has been found in jamesmartin Inline SVG up to 1.7.1 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file `lib/inline_svg/action_view/helpers.rb` of the component `URL Parameter Handler`. The manipulation of the argument filename leads to cross site scripting. The attack can be launched remotely. Upgrading to version 1.7.2 is able to address this issue. The name of the patch is f5363b351508486021f99e083c92068cf2943621. It is recommended to upgrade the affected component. The identifier VDB-217597 was assigned to this vulnerability.
|
[{'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': 'RubyGems', 'name': 'inline_svg'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.7.2'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2020-36644'}, {'type': 'WEB', 'url': 'https://github.com/jamesmartin/inline_svg/pull/117'}, {'type': 'WEB', 'url': 'https://github.com/jamesmartin/inline_svg/commit/f5363b351508486021f99e083c92068cf2943621'}, {'type': 'PACKAGE', 'url': 'https://github.com/jamesmartin/inline_svg'}, {'type': 'WEB', 'url': 'https://github.com/jamesmartin/inline_svg/releases/tag/v1.7.2'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/inline_svg/CVE-2020-36644.yml'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.217597'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.217597'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-09T21:54:19Z', 'nvd_published_at': '2023-01-07T10:15:00Z'}
|
1.4.0
|
GHSA-r5w3-xm58-jv6j
|
2023-01-10T22:01:00Z
|
2023-01-10T21:09:31Z
| null |
['CVE-2022-46176']
|
Cargo did not verify SSH host keys
|
The Rust Security Response WG was notified that Cargo did not perform SSH host key verification when cloning indexes and dependencies via SSH. An attacker could exploit this to perform man-in-the-middle (MITM) attacks.
This vulnerability has been assigned CVE-2022-46176.
## Overview
When an SSH client establishes communication with a server, to prevent MITM attacks the client should check whether it already communicated with that server in the past and what the server's public key was back then. If the key changed since the last connection, the connection must be aborted as a MITM attack is likely taking place.
It was discovered that Cargo never implemented such checks, and performed no validation on the server's public key, leaving Cargo users vulnerable to MITM attacks.
## Affected Versions
All Rust versions containing Cargo before 1.66.1 are vulnerable (prior to 0.67.1 for the crates.io package).
Note that even if you don't explicitly use SSH for alternate registry indexes or crate dependencies, you might be affected by this vulnerability if you have configured git to replace HTTPS connections to GitHub with SSH (through git's [`url.<base>.insteadOf`][1] setting), as that'd cause you to clone the crates.io index through SSH.
## Mitigations
We will be releasing Rust 1.66.1 today, 2023-01-10, changing Cargo to check the SSH host key and abort the connection if the server's public key is not already trusted. We recommend everyone to upgrade as soon as possible.
Patch files for Rust 1.66.0 are also available [here][2] for custom-built toolchains.
For the time being Cargo will not ask the user whether to trust a server's public key during the first connection. Instead, Cargo will show an error message detailing how to add that public key to the list of trusted keys. Note that this might break your automated builds if the hosts you clone dependencies or indexes from are not already trusted.
If you can't upgrade to Rust 1.66.1 yet, we recommend configuring Cargo to use the `git` CLI instead of its built-in git support. That way, all git network operations will be performed by the `git` CLI, which is not affected by this vulnerability. You can do so by adding this snippet to your [Cargo configuration file](https://doc.rust-lang.org/cargo/reference/config.html):
```toml
[net]
git-fetch-with-cli = true
```
## Acknowledgments
Thanks to the Julia Security Team for disclosing this to us according to our [security policy][3]!
We also want to thank the members of the Rust project who contributed to fixing this issue. Thanks to Eric Huss and Weihang Lo for writing and reviewing the patch, Pietro Albini for coordinating the disclosure and writing this advisory, and Josh Stone, Josh Triplett and Jacob Finkelman for advising during the disclosure.
[1]: https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf
[2]: https://github.com/rust-lang/wg-security-response/tree/main/patches/CVE-2022-46176
[3]: https://www.rust-lang.org/policies/security
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'crates.io', 'name': 'cargo'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.67.1'}]}], 'database_specific': {'last_known_affected_version_range': '<= 0.67.0'}}]
|
[{'type': 'WEB', 'url': 'https://github.com/rust-lang/cargo/security/advisories/GHSA-r5w3-xm58-jv6j'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-46176'}, {'type': 'WEB', 'url': 'https://git-scm.com/docs/git-config#Documentation/git-config.txt-urlltbasegtinsteadOf'}, {'type': 'PACKAGE', 'url': 'https://github.com/rust-lang/cargo'}, {'type': 'WEB', 'url': 'https://github.com/rust-lang/wg-security-response/tree/main/patches/CVE-2022-46176'}, {'type': 'WEB', 'url': 'https://www.rust-lang.org/policies/security'}]
|
{'cwe_ids': ['CWE-347'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-10T21:09:31Z', 'nvd_published_at': '2023-01-11T21:15:00Z'}
|
1.4.0
|
GHSA-8v53-23mx-hcf9
|
2023-01-27T01:15:05Z
|
2023-01-27T00:30:18Z
| null |
['CVE-2023-0509']
|
Improper Certificate Validation in pyload-ng
|
Improper Certificate Validation in GitHub repository pyload/pyload prior to 0.5.0b3.dev44.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'PyPI', 'name': 'pyload-ng'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.5.0b3.dev44'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0509'}, {'type': 'WEB', 'url': 'https://github.com/pyload/pyload/commit/a9098bdf7406e6faf9df3da6ff2d584e90c13bbb'}, {'type': 'PACKAGE', 'url': 'https://github.com/pyload/pyload'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/a370e0c2-a41c-4871-ad91-bc6f31a8e839'}]
|
{'cwe_ids': ['CWE-295'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-27T01:15:05Z', 'nvd_published_at': '2023-01-26T22:15:00Z'}
|
1.4.0
|
GHSA-7cxr-h8wm-fg4c
|
2023-08-31T18:47:04Z
|
2023-01-14T12:30:23Z
| null |
['CVE-2023-22602']
|
Apache Shiro Interpretation Conflict vulnerability
|
When using Apache Shiro before 1.11.0 together with Spring Boot 2.6+, a specially crafted HTTP request may cause an authentication bypass. The authentication bypass occurs when Shiro and Spring Boot are using different pattern-matching techniques. Both Shiro and Spring Boot < 2.6 default to Ant style pattern matching. Mitigation: Update to Apache Shiro 1.11.0, or set the following Spring Boot configuration value: `spring.mvc.pathmatch.matching-strategy = ant_path_matcher`
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.apache.shiro:shiro-root'}, 'ecosystem_specific': {'affected_functions': ['']}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.11.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22602'}, {'type': 'PACKAGE', 'url': 'https://github.com/apache/shiro'}, {'type': 'WEB', 'url': 'https://lists.apache.org/thread/dzj0k2smpzzgj6g666hrbrgsrlf9yhkl'}]
|
{'cwe_ids': ['CWE-436'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T21:50:25Z', 'nvd_published_at': '2023-01-14T10:15:00Z'}
|
1.4.0
|
GHSA-pm72-27mg-fc28
|
2023-02-06T16:46:41Z
|
2023-01-29T03:30:19Z
| null |
['CVE-2023-0564']
|
Froxlor contains Weak Password Requirements
|
Weak Password Requirements in GitHub repository froxlor/froxlor prior to 2.0.10.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'froxlor/froxlor'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.0.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0564'}, {'type': 'WEB', 'url': 'https://github.com/froxlor/froxlor/commit/2a84e9c1207fd3d792b7fb198fd0c66fe1a66a7a'}, {'type': 'PACKAGE', 'url': 'https://github.com/froxlor/froxlor'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/a4f86d6f-0d5d-428d-a4b3-551b20a21ce6'}]
|
{'cwe_ids': ['CWE-521'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-31T23:32:09Z', 'nvd_published_at': '2023-01-29T01:15:00Z'}
|
1.4.0
|
GHSA-cm8h-q92v-xcfc
|
2023-01-10T16:15:07Z
|
2023-01-09T21:55:44Z
| null |
['CVE-2023-22477']
|
mercurius has Uncaught Exception when using subscriptions
|
### Impact
Any users of Mercurius until version v11.5.0 are subjected to a denial of service attack by sending a malformed packet over WebSocket to `/graphql`.
### Patches
This was patched in https://github.com/mercurius-js/mercurius/pull/940.
The patch was released as v11.5.0 and v8.13.2.
### Workarounds
Disable subscriptions.
### References
Reported publicly as https://github.com/mercurius-js/mercurius/issues/939.
The same problem was solved in https://github.com/fastify/fastify-websocket/pull/228
|
[{'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': 'mercurius'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '9.0.0'}, {'fixed': '11.5.0'}]}]}, {'package': {'ecosystem': 'npm', 'name': 'mercurius'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '8.13.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/mercurius-js/mercurius/security/advisories/GHSA-cm8h-q92v-xcfc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22477'}, {'type': 'WEB', 'url': 'https://github.com/mercurius-js/mercurius/issues/939'}, {'type': 'WEB', 'url': 'https://github.com/fastify/fastify-websocket/pull/228'}, {'type': 'WEB', 'url': 'https://github.com/mercurius-js/mercurius/pull/940'}, {'type': 'PACKAGE', 'url': 'https://github.com/mercurius-js/mercurius'}]
|
{'cwe_ids': ['CWE-248'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-09T21:55:44Z', 'nvd_published_at': '2023-01-09T15:15:00Z'}
|
1.4.0
|
GHSA-vm5r-c87r-pf6x
|
2023-02-04T00:14:05Z
|
2023-01-31T22:21:48Z
| null |
['CVE-2023-22474']
|
Parse Server option `masterKeyIps` vulnerability to IP spoofing
|
### Impact
Parse Server uses the request header `x-forwarded-for` to determine the client IP address. If Parse Server doesn't run behind a proxy server, then a client can set this header and Parse Server will trust the value of the header. The incorrect client IP address will be used by various features in Parse Server. This allows to circumvent the security mechanism of the Parse Server option `masterKeyIps` by setting an allowed IP address as the `x-forwarded-for` header value.
### Patches
The mechanism to determine the client IP address has been rewritten. The correct IP address determination now requires to set the Parse Server option `trustProxy` accordingly, see the express framework's [trust proxy](https://expressjs.com/en/guide/behind-proxies.html) setting.
### References
- https://github.com/parse-community/parse-server/security/advisories/GHSA-vm5r-c87r-pf6x
- https://expressjs.com/en/guide/behind-proxies.html
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'parse-server'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '5.4.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/security/advisories/GHSA-vm5r-c87r-pf6x'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-22474'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server/commit/e016d813e083ce6828f9abce245d15b681a224d8'}, {'type': 'PACKAGE', 'url': 'https://github.com/parse-community/parse-server'}]
|
{'cwe_ids': ['CWE-290'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-31T22:21:48Z', 'nvd_published_at': '2023-02-03T20:15:00Z'}
|
1.4.0
|
GHSA-25c3-7fvj-v45j
|
2023-01-23T18:50:15Z
|
2023-01-16T00:30:24Z
| null |
['CVE-2023-0309']
|
phpMyFAQ Stored Cross-site Scripting vulnerability
|
Cross-site Scripting (XSS) - Stored in GitHub repository thorsten/phpmyfaq prior to 3.1.10.
|
[{'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': 'thorsten/phpmyfaq'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.1.10'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-0309'}, {'type': 'WEB', 'url': 'https://github.com/thorsten/phpmyfaq/commit/376d1d3e5a42edf07260e98461d2fddbee74419b'}, {'type': 'PACKAGE', 'url': 'https://github.com/thorsten/phpmyfaq'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/c03c5925-43ff-450d-9827-2b65a3307ed6'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T22:02:14Z', 'nvd_published_at': '2023-01-15T22:15:00Z'}
|
1.4.0
|
GHSA-vm74-j4wq-82xj
|
2023-01-20T23:19:16Z
|
2023-01-17T21:30:22Z
| null |
['CVE-2022-4891']
|
Sisimai Inefficient Regular Expression Complexity vulnerability
|
A vulnerability has been found in Sisimai up to 4.25.14p11 and classified as problematic. This vulnerability affects the function `to_plain` of the file `lib/sisimai/string.rb`. The manipulation leads to inefficient regular expression complexity. The exploit has been disclosed to the public and may be used. Upgrading to version 4.25.14p12 is able to address this issue. The name of the patch is 51fe2e6521c9c02b421b383943dc9e4bbbe65d4e. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-218452.
|
[]
|
[{'package': {'ecosystem': 'RubyGems', 'name': 'sisimai'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.25.14p12'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-4891'}, {'type': 'WEB', 'url': 'https://github.com/sisimai/rb-sisimai/pull/244'}, {'type': 'WEB', 'url': 'https://github.com/sisimai/rb-sisimai/commit/51fe2e6521c9c02b421b383943dc9e4bbbe65d4e'}, {'type': 'WEB', 'url': 'https://gist.githubusercontent.com/gmcabrita/e5dc0332473fc2e3a7a407434c8d21c7/raw/00b12035e5e1b685469f143b94301a50306376ba/example.html'}, {'type': 'WEB', 'url': 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/sisimai/CVE-2022-4891.yml'}, {'type': 'PACKAGE', 'url': 'https://github.com/sisimai/rb-sisimai'}, {'type': 'WEB', 'url': 'https://github.com/sisimai/rb-sisimai/releases/tag/v4.25.14p12'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.218452'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.218452'}]
|
{'cwe_ids': ['CWE-1333'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-01-20T23:19:16Z', 'nvd_published_at': '2023-01-17T20:15:00Z'}
|
1.4.0
|
GHSA-xr8x-pxm6-prjg
|
2023-01-23T22:04:47Z
|
2023-01-23T22:04:47Z
| null |
[]
|
MITM based Zip Slip in `org.hl7.fhir.publisher:org.hl7.fhir.publisher`
|
### Impact
MITM can enable Zip-Slip.
### Vulnerability
#### Vulnerability 1: `Publisher.java`
There is no validation that the zip file being unpacked has entries that are not maliciously writing outside of the intended destination directory.
https://github.com/HL7/fhir-ig-publisher/blob/87313e92de6dd6cea816449e0edd225e054a7891/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/publisher/Publisher.java#L3598-L3610
#### Vulnerability 2: `WebSourceProvider.java`
There is a check for malicious zip entries here, but it is not covered by test cases and could potentially be reverted in future changes.
https://github.com/HL7/fhir-ig-publisher/blob/87313e92de6dd6cea816449e0edd225e054a7891/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/web/WebSourceProvider.java#L104-L112
#### Vulnerability 3: `ZipFetcher.java`
This retains the path for Zip files in FetchedFile entries, which could later be used to output malicious entries to another compressed file or file system.
https://github.com/HL7/fhir-ig-publisher/blob/87313e92de6dd6cea816449e0edd225e054a7891/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/publisher/ZipFetcher.java#L57-L106
#### Vulnerability 4: `IGPack2NpmConvertor.java`
The loadZip method retains the path for entries in the zip file, which could later be used to output malicious entries to another compressed file or file system.
https://github.com/HL7/fhir-ig-publisher/blob/87313e92de6dd6cea816449e0edd225e054a7891/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/publisher/IGPack2NpmConvertor.java#L442-L463
|
[{'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': 'Maven', 'name': 'org.hl7.fhir.publisher:org.hl7.fhir.publisher'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.30'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/HL7/fhir-ig-publisher/security/advisories/GHSA-xr8x-pxm6-prjg'}, {'type': 'PACKAGE', 'url': 'https://github.com/HL7/fhir-ig-publisher'}]
|
{'cwe_ids': [], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-01-23T22:04:47Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qv66-f876-vjvr
|
2023-01-19T16:35:20Z
|
2023-01-11T15:30:28Z
| null |
['CVE-2018-25074']
|
skeemas Inefficient Regular Expression Complexity vulnerability
|
A vulnerability was found in Prestaul skeemas and classified as problematic. This issue affects some unknown processing of the file validators/base.js. The manipulation of the argument uri leads to inefficient regular expression complexity. The name of the patch is 65e94eda62dc8dc148ab3e59aa2ccc086ac448fd. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218003.
|
[{'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': 'npm', 'name': 'skeemas'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.2.5'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2018-25074'}, {'type': 'WEB', 'url': 'https://github.com/Prestaul/skeemas/commit/65e94eda62dc8dc148ab3e59aa2ccc086ac448fd'}, {'type': 'PACKAGE', 'url': 'https://github.com/Prestaul/skeemas'}, {'type': 'WEB', 'url': 'https://vuldb.com/?ctiid.218003'}, {'type': 'WEB', 'url': 'https://vuldb.com/?id.218003'}]
|
{'cwe_ids': ['CWE-1333'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-01-11T21:52:46Z', 'nvd_published_at': '2023-01-11T15:15:00Z'}
|
1.4.0
|
GHSA-mxhg-rvwx-x993
|
2023-05-23T16:23:09Z
|
2023-05-22T19:50:04Z
| null |
['CVE-2023-32688']
|
Invalid push request payload crashes Parse Server
|
### Impact
The Parse Server Push Adapter can crash Parse Server due to an invalid push notification payload.
### Patches
Invalid push notification payload is caught and an logged.
### Workarounds
n/a
### References
- https://github.com/parse-community/parse-server-push-adapter/security/advisories/GHSA-mxhg-rvwx-x993
- https://github.com/parse-community/parse-server-push-adapter/pull/217
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'parse-server-push-adapter'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.1.3'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server-push-adapter/security/advisories/GHSA-mxhg-rvwx-x993'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32688'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server-push-adapter/pull/217'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server-push-adapter/commit/598cb84d0866b7c5850ca96af920e8cb5ba243ec'}, {'type': 'PACKAGE', 'url': 'https://github.com/parse-community/parse-server-push-adapter'}, {'type': 'WEB', 'url': 'https://github.com/parse-community/parse-server-push-adapter/releases/tag/4.1.3'}]
|
{'cwe_ids': ['CWE-20'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-22T19:50:04Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9m92-qwpc-qm78
|
2023-05-17T03:32:52Z
|
2023-05-16T18:30:16Z
| null |
['CVE-2023-32994']
|
Jenkins SAML Single Sign On(SSO) Plugin unconditionally disables SSL/TLS certificate validation
|
Jenkins SAML Single Sign On(SSO) Plugin 2.1.0 and earlier unconditionally disables SSL/TLS certificate validation for connections to miniOrange or the configured IdP to retrieve SAML metadata.
This lack of validation could be abused using a man-in-the-middle attack to intercept these connections.
SAML Single Sign On(SSO) Plugin 2.2.0 performs SSL/TLS certificate validation when connecting to miniOrange or the configured IdP to retrieve SAML metadata.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'io.jenkins.plugins:miniorange-saml-sp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.2.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32994'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3001%20(2)'}]
|
{'cwe_ids': ['CWE-295'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-17T03:32:52Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q77x-cxrq-988j
|
2023-05-17T03:24:54Z
|
2023-05-16T18:30:16Z
| null |
['CVE-2023-32988']
|
Jenkins Azure VM Agents Plugin missing permission checks
|
Jenkins Azure VM Agents Plugin 852.v8d35f0960a_43 and earlier does not perform permission checks in several HTTP endpoints.
This allows attackers with Overall/Read permission to connect to an attacker-specified Azure Cloud server using attacker-specified credentials IDs obtained through another method.
Additionally, these HTTP endpoints do not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
Azure VM Agents Plugin 853.v4a_1a_dd947520 requires POST requests and the appropriate permissions for the affected HTTP endpoints.
|
[{'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': 'org.jenkins-ci.plugins:azure-vm-agents'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '853.v4a'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32988'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-2855%20(1)'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-17T03:24:54Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-7xgj-j9hp-c692
|
2023-05-30T15:40:49Z
|
2023-05-16T18:30:16Z
| null |
['CVE-2023-33006']
|
Jenkins WSO2 Oauth Plugin cross-site request forgery vulnerability
|
Jenkins WSO2 Oauth Plugin 1.0 and earlier does not implement a state parameter in its OAuth flow, a unique and non-guessable value associated with each authentication request.
This vulnerability allows attackers to trick users into logging in to the attacker’s account.
As of publication of this advisory, there is no fix.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.jenkins-ci.plugins:wso2id-oauth'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-33006'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-2990'}]
|
{'cwe_ids': ['CWE-352'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-17T03:46:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-2wvv-phhw-qvmc
|
2023-05-17T02:58:11Z
|
2023-05-16T18:30:16Z
| null |
['CVE-2023-32977']
|
Jenkins Pipeline: Job Plugin vulnerable to stored Cross-site Scripting
|
Jenkins Pipeline: Job Plugin 1292.v27d8cc3e2602 and earlier does not escape the display name of the build that caused an earlier build to be aborted, when "Do not allow concurrent builds" is set.
This results in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to set build display names immediately.
The Jenkins security team is not aware of any plugins that allow the exploitation of this vulnerability, as the build name must be set before the build starts.
Pipeline: Job Plugin 1295.v395eb_7400005 escapes the display name of the build that caused an earlier build to be aborted.
|
[{'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': 'Maven', 'name': 'org.jenkins-ci.plugins.workflow:workflow-job'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1295.v395eb'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32977'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3042'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-17T02:58:11Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-p9qp-c452-f9r7
|
2023-06-02T23:25:27Z
|
2023-05-24T17:21:33Z
| null |
['CVE-2022-39374']
|
Synapse Denial of service due to incorrect application of event authorization rules during state resolution
|
### Impact
If Synapse and a malicious homeserver are both joined to the same room, the malicious homeserver can trick Synapse into accepting previously rejected events into its view of the current state of that room. This can be exploited in a way that causes all further messages and state changes sent in that room from the vulnerable homeserver to be rejected.
Synapse homeservers are affected by this issue if and only if they are joined to rooms which members of untrusted homeservers are joined or invited to.
- Synapse homeservers in rooms available over public federation **are** affected.
- Synapse homeservers with federation disabled are not affected.
- Synapse homeservers in a closed federation containing only trusted servers are not affected.
- Synapse homeservers which are only joined to rooms with federation disabled[^1] are not affected.
### Patches
Administrators of homeservers with federation enabled are advised to upgrade to 1.68.0 or higher.
### Workarounds
* Federation can be disabled by setting [`federation_domain_whitelist`](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#federation_domain_whitelist) to an empty list (`[]`). from the vulnerable homeserver to be rejected. This issue has been patched in version 1.68.0
### References
- https://github.com/matrix-org/synapse/pull/13723
[^1]: See `m.federate` in the [`m.room.create` definition](https://spec.matrix.org/v1.4/client-server-api/#mroomcreate).
### For more information
If you have any questions or comments about this advisory, e-mail us at [security@matrix.org](mailto:security@matrix.org).
|
[{'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': 'PyPI', 'name': 'matrix-synapse'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.62.0'}, {'fixed': '1.68.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/security/advisories/GHSA-p9qp-c452-f9r7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-39374'}, {'type': 'WEB', 'url': 'https://github.com/matrix-org/synapse/pull/13723'}, {'type': 'PACKAGE', 'url': 'https://github.com/matrix-org/synapse'}, {'type': 'WEB', 'url': 'https://github.com/pypa/advisory-database/tree/main/vulns/matrix-synapse/PYSEC-2023-66.yaml'}, {'type': 'WEB', 'url': 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UJIJRP5ZH6B3KGFLHCAKR2IX2Y4Z25QD/'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-24T17:21:33Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-g7rj-q722-245g
|
2023-05-15T13:43:15Z
|
2023-05-08T18:30:17Z
| null |
['CVE-2023-2583']
|
jsreport vulnerable to code injection
|
jsreport prior to 3.11.3 had a version of vm2 vulnerable to CVE-2023-29017 hard coded in the package.json of the jsreport-core component. An attacker can use this vulnerability to obtain the authority of the jsreport playground server, or construct a malicious webpage/html file and send it to the user to attack the installed jsreport client.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'jsreport'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '3.11.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-2583'}, {'type': 'WEB', 'url': 'https://github.com/jsreport/jsreport/commit/afaff3804b34b38e959f5ae65f9e672088de13d7'}, {'type': 'PACKAGE', 'url': 'https://github.com/jsreport/jsreport'}, {'type': 'WEB', 'url': 'https://github.com/jsreport/jsreport/releases/tag/3.11.3'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/397ea68d-1e28-44ff-b830-c8883d067d96'}]
|
{'cwe_ids': ['CWE-94'], 'severity': 'CRITICAL', 'github_reviewed': True, 'github_reviewed_at': '2023-05-09T19:16:18Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-r9xw-p7wj-w792
|
2023-05-17T21:33:32Z
|
2023-05-10T15:30:22Z
| null |
['CVE-2023-27564']
|
n8n Information Disclosure vulnerability
|
The n8n package prior to 0.216.1 for Node.js allows Information Disclosure.
|
[{'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': 'n8n'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.216.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27564'}, {'type': 'PACKAGE', 'url': 'https://github.com/n8n-io/n8n'}, {'type': 'WEB', 'url': 'https://github.com/n8n-io/n8n/releases'}, {'type': 'WEB', 'url': 'https://github.com/n8n-io/n8n/releases/tag/n8n%400.216.1'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20230622-0007/'}, {'type': 'WEB', 'url': 'https://www.synacktiv.com/sites/default/files/2023-05/Synacktiv-N8N-Multiple-Vulnerabilities_0.pdf'}]
|
{'cwe_ids': ['CWE-668'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-11T20:46:13Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-q3p4-v2cm-q945
|
2023-05-22T20:29:59Z
|
2023-05-16T12:30:25Z
| null |
['CVE-2023-2730']
|
Pimcore Cross-site Scripting vulnerability
|
Pimcore prior to 10.3.3 is vulnerable to stored cross-site scripting at the `Title field` in `SEO & Settings` tab of `Document`.
|
[{'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/pimcore'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '10.3.3'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-2730'}, {'type': 'WEB', 'url': 'https://github.com/pimcore/pimcore/commit/8ab06bfbb5a05a1b190731d9c7476ec45f5ee878'}, {'type': 'PACKAGE', 'url': 'https://github.com/pimcore/pimcore'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/6c6f5c26-d545-4e7b-82bb-1fe28006c885'}]
|
{'cwe_ids': ['CWE-79'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-16T17:30:52Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9qpj-qq2r-5mcc
|
2023-05-26T13:52:19Z
|
2023-05-26T13:52:19Z
| null |
['CVE-2023-33187']
|
html inputs of type password recorded in plaintext when converted to text inputs
|
### Impact
Highlight may record passwords on customer deployments when a password html input is switched to `type="text"` via a javascript "Show Password" button. This differs from the expected behavior which always obfuscates `type="password"` inputs. A customer may assume that switching to `type="text"` would also not record this input; hence, they would not add additional `highlight-mask` css-class obfuscation to this part of the DOM, resulting in unintentional recording of a password value when a `Show Password` button is used.
### Patches
`highlight.run@6.0.0` resolves the issue via https://github.com/rrweb-io/rrweb/pull/1184
This patch tracks changes to the `type` attribute of an input to ensure an input that used to be a `type="password"` continues to be obfuscated.
### Workarounds
We have deployed a change to our data ingest to obfuscate passwords server side from older clients.
This means that upgrading to the latest version of highlight.run is not necessary but recommended to prevent potential network transfer of recorded password data to our backend.
### References
https://github.com/rrweb-io/rrweb/pull/1184
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'highlight.run'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '6.0.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/highlight/highlight/security/advisories/GHSA-9qpj-qq2r-5mcc'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-33187'}, {'type': 'WEB', 'url': 'https://github.com/rrweb-io/rrweb/pull/1184'}, {'type': 'PACKAGE', 'url': 'https://github.com/highlight/highlight'}]
|
{'cwe_ids': ['CWE-319'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-26T13:52:19Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xp5g-jhg3-3rg2
|
2023-05-30T23:12:12Z
|
2023-05-22T00:30:20Z
| null |
['CVE-2023-33252']
|
Double spend in snarkjs
|
iden3 snarkjs through 0.6.11 allows double spending because there is no validation that the publicSignals length is less than the field modulus.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'snarkjs'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '0.6.11'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-33252'}, {'type': 'PACKAGE', 'url': 'https://github.com/iden3/snarkjs'}, {'type': 'WEB', 'url': 'https://github.com/iden3/snarkjs/commits/master/src/groth16_verify.js'}, {'type': 'WEB', 'url': 'https://github.com/iden3/snarkjs/tags'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-22T19:37:12Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-xf96-w227-r7c4
|
2023-06-08T16:33:52Z
|
2023-05-26T18:30:21Z
| null |
['CVE-2023-20883']
|
Spring Boot Welcome Page Denial of Service
|
In Spring Boot versions 3.0.0 - 3.0.6, 2.7.0 - 2.7.11, 2.6.0 - 2.6.14, 2.5.0 - 2.5.14 and older unsupported versions, there is potential for a denial-of-service (DoS) attack if Spring MVC is used together with a reverse proxy cache.
Specifically, an application is vulnerable if all of the conditions are true:
* The application has Spring MVC auto-configuration enabled. This is the case by default if Spring MVC is on the classpath.
* The application makes use of Spring Boot's welcome page support, either static or templated.
* Your application is deployed behind a proxy which caches 404 responses.
Your application is NOT vulnerable if any of the following are true:
* Spring MVC auto-configuration is disabled. This is true if WebMvcAutoConfiguration is explicitly excluded, if Spring MVC is not on the classpath, or if spring.main.web-application-type is set to a value other than SERVLET.
* The application does not use Spring Boot's welcome page support.
* You do not have a proxy which caches 404 responses.
Affected Spring Products and Versions
Spring Boot
3.0.0 to 3.0.6 2.7.0 to 2.7.11 2.6.0 to 2.6.14 2.5.0 to 2.5.14
Older, unsupported versions are also affected
Mitigation
Users of affected versions should apply the following mitigations:
* 3.0.x users should upgrade to 3.0.7+
* 2.7.x users should upgrade to 2.7.12+
* 2.6.x users should upgrade to 2.6.15+
* 2.5.x users should upgrade to 2.5.15+
Users of older, unsupported versions should upgrade to 3.0.7+ or 2.7.12+.
Workarounds: configure the reverse proxy not to cache 404 responses and/or not to cache responses to requests to the root (/) of the application.
|
[{'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.springframework.boot:spring-boot-autoconfigure'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.0.0'}, {'fixed': '3.0.7'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.springframework.boot:spring-boot-autoconfigure'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.7.0'}, {'fixed': '2.7.12'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.springframework.boot:spring-boot-autoconfigure'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.6.0'}, {'fixed': '2.6.15'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.springframework.boot:spring-boot-autoconfigure'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '2.5.15'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-20883'}, {'type': 'WEB', 'url': 'https://github.com/spring-projects/spring-boot/issues/35552'}, {'type': 'WEB', 'url': 'https://github.com/spring-projects/spring-boot/commit/418dd1ba5bdad79b55a043000164bfcbda2acd78'}, {'type': 'PACKAGE', 'url': 'https://github.com/spring-projects/spring-boot'}, {'type': 'WEB', 'url': 'https://github.com/spring-projects/spring-boot/releases/tag/v2.5.15'}, {'type': 'WEB', 'url': 'https://github.com/spring-projects/spring-boot/releases/tag/v2.6.15'}, {'type': 'WEB', 'url': 'https://github.com/spring-projects/spring-boot/releases/tag/v2.7.12'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20230703-0008/'}, {'type': 'WEB', 'url': 'https://spring.io/security/cve-2023-20883'}]
|
{'cwe_ids': ['CWE-400'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-26T22:09:06Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gw42-f939-fhvm
|
2023-07-20T18:57:26Z
|
2023-05-23T19:54:30Z
| null |
['CVE-2023-32315']
|
Administration Console authentication bypass in openfire xmppserver
|
An important security issue affects a range of versions of Openfire, the cross-platform real-time collaboration server based on the XMPP protocol that is created by the Ignite Realtime community.
### Impact
Openfire's administrative console (the Admin Console), a web-based application, was found to be vulnerable to a path traversal attack via the setup environment. This permitted an unauthenticated user to use the unauthenticated Openfire Setup Environment in an already configured Openfire environment to access restricted pages in the Openfire Admin Console reserved for administrative users.
### Cause
Path traversal protections were already in place to protect against exactly this kind of attack, but didn’t defend against certain non-standard URL encoding for UTF-16 characters, that were not supported by the embedded webserver that was in use at the time.
A later upgrade of the embedded webserver included support for non-standard URL encoding of UTF-16 characters. The path traversal protections in place in Openfire were not updated to include protection against this new encoding.
Openfire's API defines a mechanism for certain URLs to be excluded from web authentication (this, for example, is used for the login page). This mechanism allows for wildcards to be used, to allow for flexible URL pattern matching.
The combination of the wildcard pattern matching and path traversal vulnerability allows a malicious user to bypass authentication requirements for Admin Console pages.
### Affected versions
This vulnerability affects all versions of Openfire that have been released since April 2015, starting with version 3.10.0. The problem has been patched in Openfire release 4.7.5 and 4.6.8, and further improvements will be included in the yet-to-be released first version on the 4.8 branch (which is expected to be version 4.8.0).
### Problem Reproduction
To test if an instance of Openfire is affected, follow these steps. Open a browser in incognito mode, or otherwise ensure that there is no authenticated session with the Openfire admin console. Open the following URL (possibly modified for the hostname of the server that is running Openfire):
```http://localhost:9090/setup/setup-s/%u002e%u002e/%u002e%u002e/log.jsp```
If this shows part of the openfire logfiles, then the instance of Openfire is affected by this vulnerability. Note that different versions of Openfire will show a different layout. Newer versions of Openfire can be expected to show log files on a dark background, while older versions will show a largely white page. (Depending on the content of the log file, this page might be empty, apart from a header!)
If there's a redirect to the login page, the instance is likely unaffected.
### Problem Resolution
The problem has been patched in [Openfire release 4.7.5 and 4.6.8](https://www.igniterealtime.org/downloads/#openfire), and further improvements will be included in the yet-to-be released first version on the 4.8 branch (which is expected to be version 4.8.0).
- In Openfire 4.6.8, 4.7.5 and 4.8.0, Path Traversal pattern detection has been improved to include detection of non-standard URL encodings, preventing any non UTF-8 characters.
- In Openfire 4.6.8, 4.7.5 and 4.8.0, a new configuration property (`adminConsole.access.allow-wildcards-in-excludes`) is introduced that controls the permissibility of using wildcards in URL-patterns that define exclusions to authentication.
- In Openfire 4.6.8, 4.7.5 and 4.8.0, the existing value that uses a wildcard in URL-patterns that define exclusions to authentication has been replaced by values that do not depend on a wildcard.
- In Openfire 4.6.8, 4.7.5 and 4.8.0, Setup-specific URL-patterns that define exclusions to authentication are no longer active after the setup process has finished.
- In Openfire 4.8.0, the embedded webserver will be updated to a version that no longer supports the non-standard URL encoding of UTF-16 characters.
- In Openfire 4.8.0, the embedded webserver that serves the Openfire administrative console will bind to the loopback network interface by default.
Be aware that the new configuration properties can interfere with the functionality of certain Openfire plugins. This is especially true for plugins that bind a (web)endpoint to the embedded webserver that serves the Openfire administrative console, like current versions of the REST API plugin do. For these plugins to remain functional and/or reachable, it might be required to toggle the property `adminConsole.access.allow-wildcards-in-excludes` to `true`, and to avoid binding the embedded webserver to the loopback network interface only.
When your server uses older versions of the following plugins, make sure to upgrade them:
- [Random Avatar plugin](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=randomavatar), update to version 1.1.0 or later.
- [Monitoring Service plugin](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=monitoring), update to version 2.5.0 or later.
- [HTTP File Upload plugin](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=httpfileupload), update to version 1.3.0 or later.
### Mitigation
If an Openfire upgrade isn’t available for your release, or isn’t quickly actionable, you can take any of the following steps to mitigate the risk for your Openfire environment.
Be aware: through Openfire plugins, the effectiveness of some mitigations listed below can be reduced, while other mitigations might affect the functionality of plugins. Particular care should be taken when using the Monitoring Service plugin, REST API plugin, User Service plugin and/or Random Avatar plugin.
#### Restrict network access
Use network security measures (network ACLs and/or firewalls, VPNs) to ensure only trusted members of your community have access to the Openfire Admin Console. As a general rule, never expose the Openfire Admin Console to the general internet.
Examples:
* On a linux machine running `ufw`, deny ports 9090 and 9091 on non-loopback interfaces
* On a Windows machine, restrict the rules that open ports 9090 and 9091 to only allow traffic from the IPv4 and/or IPv6 loopback addresses
* On AWS cloud infrastructure, use EC2 Security Groups to restrict ports 9090 and 9091 to trusted IP addresses. If the trusted range is necessarily too broad, consider opening and closing the ports only as necessary
* If using Docker, instead of `docker run ... -p 5222:5222 -p 9090:9090 -p 9091:9091 openfire` prevent remote access to the Admin Console with `docker run ... -p 5222:5222 -p 127.0.0.1:9090:9090 -p 127.0.0.1:9091:9091 openfire`
#### Modify runtime configuration file
To close the avenue of potential attack, a runtime configuration file of Openfire can be modified.
In Openfire's installation directory, find the file `plugins/admin/webapp/WEB-INF/web.xml`. After creating a backup of this file, edit the original file.
The content of this file is XML. Find a `<filter>` element, that contains the `<filter-name>AuthCheck</filter-name>` child element. Depending on your version of Openfire, it will look similar to this:
```xml
<filter>
<filter-name>AuthCheck</filter-name>
<filter-class>org.jivesoftware.admin.AuthCheckFilter</filter-class>
<init-param>
<param-name>excludes</param-name>
<param-value>
login.jsp,index.jsp?logout=true,setup/index.jsp,setup/setup-*,.gif,.png,error-serverdown.jsp,loginToken.jsp
</param-value>
</init-param>
</filter>
```
The value inside of the `param-value` element is a comma-separated list of values. From this list, remove all `*` (asterisk) characters.
Save the file, and restart Openfire for the change to take effect.
Note that no guarantees can be given that this runtime configuration change persists over time. Ensure to monitor the presence of the fix. It is recommended to upgrade to a safe version of Openfire as soon as possible.
A side-effect of this change is that the Openfire web-based setup wizard will not function properly (functionality can be restored by reverting the change). This wizard is typically used only when initially installing Openfire.
#### Bind admin console to loopback interface
The Openfire admin console is a web-based application. By default, the corresponding webserver (that is embedded in Openfire) binds to all network interfaces of the host that it is running on.
The admin console can be configured to bind to a specific network interface. This will prevent it from being accessed through other network interfaces. By configuring the admin console to bind to the local loopback interface, it is accessible only to users on the server itself. This reduces the avenue of attack.
Note that several Openfire plugins expose part or all of their functionality through the admin console webserver. The REST API plugin, for example, serves its endpoints via this webserver. Availability of this functionality will be affected by binding the webserver to a specific network interface.
To bind the webserver of the Openfire admin console to a specific network interface, the 'openfire.xml' configuration file can be used.
In Openfire's installation directory, locate the file `conf/openfire.xml`. After creating a backup of this file, edit the original file.
The content of this file is XML. Find the `<adminConsole>` element that is a direct child element of the root `<jive>` element. Add a new element, named `<interface>` as a child element of `<adminConsole>`. The value of the `<interface>` element should be the name of the loopback interface or interface address. Setting value to `127.0.0.1` works on all tested environments (using values like `lo` on most Linux systems or `lo0` on macOS will have the same effect).
The resulting fragment of the `openfire.xml` file will look similar to this:
```xml
<?xml version="1.0" encoding="UTF-8"?>
<jive>
<adminConsole>
<interface>127.0.0.1</interface>
<port>9090</port>
<securePort>9091</securePort>
</adminConsole>
...
```
Save the file, and restart Openfire for the change to take effect.
#### Use AuthFilterSanitizer plugin
The Ignite Realtime community has made available a new plugin, called the AuthFilterSanitizer plugin. The plugin can be installed from the Openfire admin console, or can be downloaded from [the plugin's archive page](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=authfiltersanitizer) on the IgniteRealtime.org community website.
This plugin periodically removes entries for Openfire's authentication filter that are susceptible to abuse, closing the avenue of potential attack.
Note that this plugin might interfere with functionality that depends on the abuse-susceptible entries in the authentication filter that might be provided by plugins.
### Credit
This issue was originally reported by Siebene@ who has our gratitude for the responsible and detailed disclosure of the issue!
We are grateful for the resources made available by Surevine ltd. They were instrumental in addressing the issue listed in this advisory.
### References
- [Ignite Realtime community site](https://www.igniterealtime.org/)
- [Openfire releases download page](https://www.igniterealtime.org/downloads/#openfire)
- [Openfire AuthFilter Sanitizer plugin releases download page](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=authfiltersanitizer)
- [Openfire HTTP File Upload plugin releases download page](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=httpfileupload)
- [Openfire Monitoring Service plugin releases download page](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=monitoring)
- [Openfire Random Avatar plugin releases download page](https://www.igniterealtime.org/projects/openfire/plugin-archive.jsp?plugin=randomavatar)
- [OWASP: Path Traversal](https://owasp.org/www-community/attacks/Path_Traversal)
- [Wikipedia: URL encoding, section 'Non-standard implementations'](https://en.wikipedia.org/wiki/URL_encoding#Non-standard_implementations)
- [Issue OF-2595 in Openfire's issue tracker](https://igniterealtime.atlassian.net/browse/OF-2595)
- [Jetty CVE-2021-34429](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-34429)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'org.igniterealtime.openfire:xmppserver'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.10.0'}, {'fixed': '4.6.8'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'org.igniterealtime.openfire:xmppserver'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.7.0'}, {'fixed': '4.7.5'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/igniterealtime/Openfire/security/advisories/GHSA-gw42-f939-fhvm'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32315'}, {'type': 'WEB', 'url': 'https://github.com/igniterealtime/Openfire/commit/2ac00a1ff42f5d3547ef58e21f8cdec992bfcf97'}, {'type': 'WEB', 'url': 'https://github.com/igniterealtime/Openfire/commit/71f3def2adeaac62729cf544b645c6819c3d9868'}, {'type': 'WEB', 'url': 'https://github.com/igniterealtime/Openfire/commit/a3b5ebd5032ff7be9d3ada5bf52bea2df96ec881'}, {'type': 'PACKAGE', 'url': 'https://github.com/igniterealtime/Openfire'}, {'type': 'WEB', 'url': 'https://github.com/igniterealtime/Openfire/releases/tag/v4.6.8'}, {'type': 'WEB', 'url': 'https://github.com/igniterealtime/Openfire/releases/tag/v4.7.5'}, {'type': 'WEB', 'url': 'https://igniterealtime.atlassian.net/browse/OF-2595'}, {'type': 'WEB', 'url': 'http://packetstormsecurity.com/files/173607/Openfire-Authentication-Bypass-Remote-Code-Execution.html'}]
|
{'cwe_ids': ['CWE-22'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-23T19:54:30Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-jmp2-wc4p-wfh2
|
2023-05-05T02:25:00Z
|
2023-05-05T02:25:00Z
| null |
['CVE-2023-30844']
|
Mutagen list and monitor operations do not neutralize control characters in text controlled by remote endpoints
|
### Impact
Mutagen command line operations, as well as the log output from `mutagen daemon run`, are susceptible to control characters that could be provided by remote endpoints. This can cause terminal corruption, either intentional or unintentional, if these characters are present in error messages, file paths/names, and/or log output. This could be used as an attack vector if synchronizing with an untrusted remote endpoint, synchronizing files not under control of the user, or forwarding to/from an untrusted remote endpoint. On very old systems with terminals susceptible to issues such as [CVE-2003-0069](https://nvd.nist.gov/vuln/detail/CVE-2003-0069), the issue could theoretically cause code execution.
### Patches
The problem has been patched in Mutagen v0.16.6 and v0.17.1. Earlier versions of Mutagen are no longer supported and will not be patched. Versions of Mutagen after v0.18.0 will also have the patch merged.
One caveat is that the templating functionality of Mutagen's `list` and `monitor` commands has been only partially patched. In particular, the `json` template function already provided escaping and no patching was necessary. However, raw template output has been left unescaped because this raw output may be necessary for commands which embed Mutagen. To aid these commands, a new `shellSanitize` template function has been added which provides control character neutralization in strings.
### Workarounds
Avoiding synchronization of untrusted files or interaction with untrusted remote endpoints should mitigate any risk.
### References
A similar issue can be seen in kubernetes/kubernetes#101695.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/mutagen-io/mutagen'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.16.6'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mutagen-io/mutagen-compose'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.17.1'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/mutagen-io/mutagen'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.17.0'}, {'fixed': '0.17.1'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/mutagen-io/mutagen/security/advisories/GHSA-jmp2-wc4p-wfh2'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-30844'}, {'type': 'PACKAGE', 'url': 'https://github.com/mutagen-io/mutagen'}, {'type': 'WEB', 'url': 'https://github.com/mutagen-io/mutagen/releases/tag/v0.16.6'}, {'type': 'WEB', 'url': 'https://github.com/mutagen-io/mutagen/releases/tag/v0.17.1'}]
|
{'cwe_ids': ['CWE-116', 'CWE-150'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-05-05T02:25:00Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-97cp-mr4m-9mcf
|
2023-05-17T21:33:20Z
|
2023-05-10T15:30:22Z
| null |
['CVE-2023-27563']
|
n8n Privilege Escalation vulnerability
|
The n8n package prior to 0.216.1 for Node.js allows Escalation of Privileges.
|
[{'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': 'npm', 'name': 'n8n'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.216.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-27563'}, {'type': 'PACKAGE', 'url': 'https://github.com/n8n-io/n8n'}, {'type': 'WEB', 'url': 'https://github.com/n8n-io/n8n/releases'}, {'type': 'WEB', 'url': 'https://github.com/n8n-io/n8n/releases/tag/n8n%400.216.1'}, {'type': 'WEB', 'url': 'https://security.netapp.com/advisory/ntap-20230622-0007/'}, {'type': 'WEB', 'url': 'https://www.synacktiv.com/sites/default/files/2023-05/Synacktiv-N8N-Multiple-Vulnerabilities_0.pdf'}]
|
{'cwe_ids': [], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-11T20:45:04Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-w3f6-pc54-gfw7
|
2023-06-19T16:55:05Z
|
2023-05-18T17:28:39Z
| null |
['CVE-2022-24667']
|
swift-nio-http2 vulnerable to denial of service via mishandled HPACK variable length integer encoding
|
A program using swift-nio-http2 is vulnerable to a denial of service attack, caused by a network peer sending a specially crafted HPACK-encoded header block. This attack affects all swift-nio-http2 versions from 1.0.0 to 1.19.1. It is fixed in 1.19.2 and later releases.
There are a number of implementation errors in the parsing of HPACK-encoded header blocks that allow maliciously crafted HPACK header blocks to cause crashes in processes using swift-nio-http2. Each of these crashes is triggered instead of an integer overflow.
A malicious HPACK header block could be sent on any of the HPACK-carrying frames in a HTTP/2 connection (HEADERS and PUSH_PROMISE), at any position.
Sending a HPACK header block does not require any special permission, so any HTTP/2 connection peer may send one. For clients, this means any server to which they connect may launch this attack. For servers, anyone they allow to connect to them may launch such an attack.
The attack is low-effort: it takes very little resources to send an appropriately crafted field block. The impact on availability is high: receiving a frame carrying this field block immediately crashes the server, dropping all in-flight connections and causing the service to need to restart. It is straightforward for an attacker to repeatedly send appropriately crafted field blocks, so attackers require very few resources to achieve a substantial denial of service.
The attack does not have any confidentiality or integrity risks in and of itself: swift-nio-http2 is parsing the field block in memory-safe code and the crash is triggered instead of an integer overflow. However, sudden process crashes can lead to violations of invariants in services, so it is possible that this attack can be used to trigger an error condition that has confidentiality or integrity risks.
The risk can be mitigated if untrusted peers can be prevented from communicating with the service. This mitigation is not available to many services.
The issue is fixed by rewriting the parsing code to correctly handle all conditions in the function. The principal issue was found by automated fuzzing by oss-fuzz, but several associated bugs in the same code were found by code audit and fixed at the same time.
|
[{'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': 'purl-type:swift', 'name': 'github.com/apple/swift-nio-http2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '1.0.0'}, {'fixed': '1.19.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/apple/swift-nio-http2/security/advisories/GHSA-w3f6-pc54-gfw7'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2022-24667'}, {'type': 'WEB', 'url': 'https://github.com/apple/swift-nio-http2/commit/56c60a29b1207a731be62fb68cc98246942145ed'}, {'type': 'PACKAGE', 'url': 'https://github.com/apple/swift-nio-http2'}, {'type': 'WEB', 'url': 'https://github.com/apple/swift-nio-http2/releases/tag/1.19.2'}]
|
{'cwe_ids': ['CWE-190'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-18T17:28:39Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-m6m9-gr85-79vm
|
2023-05-10T21:26:32Z
|
2023-05-10T21:26:32Z
| null |
['CVE-2023-2614']
|
Pimcore Cross-site Scripting (XSS) in name field of Custom Reports
|
### Impact
This vulnerability has the potential to steal a user's cookie and gain unauthorized access to that user's account through the stolen cookie or redirect users to other malicious sites.
### Patches
Update to version 10.5.21 or apply this patch manually:
https://github.com/pimcore/pimcore/commit/c36ef54ce33f7b5e74b7b0ab9eabfed47c018fc7.patch
### Workarounds
Apply patches manually:
https://github.com/pimcore/pimcore/commit/c36ef54ce33f7b5e74b7b0ab9eabfed47c018fc7.patch
### References
https://huntr.dev/bounties/1a5e6c65-2c5e-4617-9411-5b47a7e743a6/
|
[]
|
[{'package': {'ecosystem': 'Packagist', 'name': 'pimcore/pimcore'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '10.5.21'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/pimcore/pimcore/security/advisories/GHSA-m6m9-gr85-79vm'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-2614'}, {'type': 'WEB', 'url': 'https://github.com/pimcore/pimcore/commit/c36ef54ce33f7b5e74b7b0ab9eabfed47c018fc7'}, {'type': 'PACKAGE', 'url': 'https://github.com/pimcore/pimcore'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/1a5e6c65-2c5e-4617-9411-5b47a7e743a6'}]
|
{'cwe_ids': [], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-10T21:26:32Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-w7jw-q4fg-qc4c
|
2023-05-24T17:30:16Z
|
2023-05-24T17:30:16Z
| null |
['CVE-2023-32698']
|
nfpm has incorrect default permissions
|
### Summary
When building packages directly from source control, file permissions on the checked-in files are not maintained.
### Details
When building packages directly from source control, file permissions on the checked-in files are not maintained. When nfpm packaged the files (without extra config for enforcing its own permissions) files could go out with bad permissions (chmod 666 or 777).
### PoC
Create a default nfpm structure.
Within the test folder, create 3 files named `chmod-XXX.sh`. Each script has file
permissions set corresponding with their file names (`chmod-777.sh` = `chmod 777`). Below each
file and permissions can be seen.
```console
$ ls -lart test
total 24
-rwxrwxrwx 1 user group 11 May 19 13:15 chmod-777.sh
-rw-rw-rw- 1 user group 11 May 19 13:16 chmod-666.sh
drwxr-xr-x 5 user group 160 May 19 13:19 .
-rw-rw-r-- 1 user group 11 May 19 13:19 chmod-664.sh
drwxr-xr-x 10 user group 320 May 19 13:29 ..
```
Below is the snippet nfpm configuration file of the contents of the package. The test folder
and files has no extra config for enforcing permissions.
```yaml
contents:
- src: foo-binary
dst: /usr/bin/bar
- src: bar-config.conf
dst: /etc/foo-binary/bar-config.conf
type: config
- src: test
dst: /etc/test/scripts
```
The next step is to create a deb package.
```console
$ nfpm package -p deb # Create dep package
using deb packager...
created package: foo_1.0.0_arm64.deb
```
When on a Ubuntu VM, install the foo package which was created
```console
$ sudo dpkg -i foo_1.0.0_arm64.deb # Installing deb package within Ubuntu
Selecting previously unselected package foo.
(Reading database ... 67540 files and directories currently installed.)
Preparing to unpack foo_1.0.0_arm64.deb ...
Unpacking foo (1.0.0) ...
Setting up foo (1.0.0) ...
```
Looking at `/etc/test/scripts` and viewing the permissions. Permissions are passed exactly the same as the source.
```console
$ ls -lart /etc/test/scripts
total 20
-rwxrwxrwx 1 root root 11 May 22 12:15 chmod-777.sh
-rw-rw-rw- 1 root root 11 May 22 12:16 chmod-666.sh
-rw-rw-r-- 1 root root 11 May 22 12:19 chmod-664.sh
drwxr-xr-x 3 root root 4096 May 22 13:00 ..
drwxr-xr-x 2 root root 4096 May 22 13:00 .
```
## Solution
To prevent world-writable files from making it into the packages, add the ability to override the default permissions of packaged files using a umask config option in the packaging spec file. This feature in nfpm would allow applying a global umask across any files being packaged, therefore, with the correct configuration, preventing world-writable files without needing to list permissions on each and every file in the package
### Impact
Vulnerability is https://cwe.mitre.org/data/definitions/276.html
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Anyone using nfpm for creating packages and not checking/setting file permissions before packaging could result in bad permissions for files/folders.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/goreleaser/nfpm/v2'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '2.0.0'}, {'fixed': '2.29.0'}]}]}, {'package': {'ecosystem': 'Go', 'name': 'github.com/goreleaser/nfpm'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0.1.0'}, {'fixed': '2.29.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/goreleaser/nfpm/security/advisories/GHSA-w7jw-q4fg-qc4c'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32698'}, {'type': 'WEB', 'url': 'https://github.com/goreleaser/nfpm/commit/ed9abdf63d5012cc884f2a83b4ab2b42b3680d30'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-w7jw-q4fg-qc4c'}, {'type': 'PACKAGE', 'url': 'https://github.com/goreleaser/nfpm'}, {'type': 'WEB', 'url': 'https://github.com/goreleaser/nfpm/releases/tag/v2.29.0'}]
|
{'cwe_ids': ['CWE-276'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-24T17:30:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gvrq-cg5r-7chp
|
2023-05-12T20:20:19Z
|
2023-05-12T20:20:19Z
| null |
['CVE-2023-32081']
|
Vert.x STOMP server process client frames that would not send initially a connect frame
|
### Impact
A Vert.x STOMP server processes client STOMP frames without checking that the client send an initial CONNECT frame replied with a successful CONNECTED frame. The client can subscribe to a destination or publish message without prior authentication. Any Vert.x STOMP server configured with an authentication handler is impacted.
### Patches
The issue is patched in Vert.x 4.4.2 and Vert.x 3.9.16
### Workarounds
No trivial workaround.
|
[{'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': 'Maven', 'name': 'io.vertx:vertx-stomp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '3.1.0'}, {'fixed': '3.9.16'}]}]}, {'package': {'ecosystem': 'Maven', 'name': 'io.vertx:vertx-stomp'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '4.0.0'}, {'fixed': '4.4.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vert-x3/vertx-stomp/security/advisories/GHSA-gvrq-cg5r-7chp'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-32081'}, {'type': 'WEB', 'url': 'https://github.com/vert-x3/vertx-stomp/commit/0de4bc5a44ddb57e74d92c445f16456fa03f265b'}, {'type': 'PACKAGE', 'url': 'https://github.com/vert-x3/vertx-stomp'}]
|
{'cwe_ids': ['CWE-287'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-12T20:20:19Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qmqw-r4x6-3w2q
|
2023-05-12T15:24:21Z
|
2023-05-09T06:30:25Z
| null |
['CVE-2023-2590']
|
Answer Missing Authorization vulnerability
|
A missing authorization in GitHub repository answerdev/answer prior to 1.0.9 can lead to a user rating their own answer as the best answer.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/answerdev/answer'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.0.9'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-2590'}, {'type': 'WEB', 'url': 'https://github.com/answerdev/answer/commit/51ac1e6b76ae9ab3ca2008ca4819c0cc3bd2fcd3'}, {'type': 'PACKAGE', 'url': 'https://github.com/answerdev/answer'}, {'type': 'WEB', 'url': 'https://huntr.dev/bounties/a4238a30-3ddb-4415-9055-e179c3d4dea7'}]
|
{'cwe_ids': ['CWE-862'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-05-11T20:36:13Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-qvqg-6rp8-4p9h
|
2023-05-11T20:40:16Z
|
2023-05-11T20:40:16Z
| null |
[]
|
github.com/ipfs/kubo affected by DOS Bitswap unbounded persistent memory leak
|
### Impact
An attacker is able allocate arbitrarily many bytes in the Bitswap server by sending many `WANT_BLOCK` and or `WANT_HAVE` requests which are queued in an unbounded queue, with allocations that persist even if the connection is closed.
This affects users accepting or connecting untrusted connections such as by running in the public swarm and no pnet config.
Nodes that are not publicly reachable but connects to untrusted nodes are also vulnerable to the untrusted nodes being connected to since libp2p connections are blindly bidirectional.
### Patches
- 19feb15833c6f4d6e7f1e1b132efaae96d76481d [`boxo`](https://github.com/ipfs/boxo) update in Kubo
- GHSA-m974-xj4j-7qv5 patches in boxo
### Workarounds
Use [PNET](https://github.com/ipfs/kubo/blob/master/docs/experimental-features.md#private-networks), [swarm filters](https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmaddrfilters) or [resource manager allows list](https://pkg.go.dev/github.com/libp2p/go-libp2p/p2p/host/resource-manager#readme-allowlisting-multiaddrs-to-mitigate-eclipse-attacks) to block untrusted connections.
Note that using the resource manager will disrupt both client and server features because the bitswap protocol is a message based protocol mixing requests and responses.
### References
- GHSA-m974-xj4j-7qv5
- [CVE-2023-25568](https://nvd.nist.gov/vuln/detail/CVE-2023-25568)
|
[{'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': 'Go', 'name': 'github.com/ipfs/kubo'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '0.19.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/ipfs/boxo/security/advisories/GHSA-m974-xj4j-7qv5'}, {'type': 'WEB', 'url': 'https://github.com/ipfs/kubo/security/advisories/GHSA-qvqg-6rp8-4p9h'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-25568'}, {'type': 'PACKAGE', 'url': 'https://github.com/ipfs/kubo'}]
|
{'cwe_ids': ['CWE-400', 'CWE-770'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-11T20:40:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-9cfh-vx93-84vv
|
2023-05-10T19:20:16Z
|
2023-05-10T19:20:16Z
| null |
['CVE-2023-31136']
|
PostgresNIO processes unencrypted bytes from man-in-the-middle
|
### Impact
Any user of PostgresNIO connecting to servers with TLS enabled is vulnerable to a man-in-the-middle attacker injecting false responses to the client's first few queries, despite the use of TLS certificate verification and encryption.
_The remaining text in this section is quoted verbatim from [PostgreSQL's CVE-2021-23222 advisory](https://www.postgresql.org/support/security/CVE-2021-23222/):_
> If more preconditions hold, the attacker can exfiltrate the client's password or other confidential data that might be transmitted early in a session. The attacker must have a way to trick the client's intended server into making the confidential data accessible to the attacker. A known implementation having that property is a PostgreSQL configuration vulnerable to [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/). As with any exploitation of [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/), the server must be using trust authentication with a clientcert requirement or using cert authentication. To disclose a password, the client must be in possession of a password, which is atypical when using an authentication configuration vulnerable to [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/). The attacker must have some other way to access the server to retrieve the exfiltrated data (a valid, unprivileged login account would be sufficient).
### Patches
The vulnerability is addressed in PostgresNIO versions starting from [1.14.2](https://github.com/vapor/postgres-nio/releases/tag/1.14.2) via [2df54bc94607f44584ae6ffa74e3cd754fffafc7](https://github.com/vapor/postgres-nio/commit/2df54bc94607f44584ae6ffa74e3cd754fffafc7), which required [additional support](https://github.com/apple/swift-nio/pull/2419) from SwiftNIO.
### Workarounds
There are no known workarounds for unpatched users.
### Additional Credits
Special thanks to PostgreSQL's Tom Lane <[tgl@sss.pgh.pa.us](mailto:tgl@sss.pgh.pa.us)> for reporting this issue!
### References
- [PostgreSQL security advisory for CVE-2021-23222](https://www.postgresql.org/support/security/CVE-2021-23222/)
- [GitHub security advisory GHSA-735f-7qx4-jqq5 for CVE-2021-23222](https://github.com/advisories/GHSA-735f-7qx4-jqq5)
- [PostgreSQL security advisory for CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/)
- [GitHub security advisory GHSA-467w-rrqc-395f for CVE-2021-23214](https://github.com/advisories/GHSA-467w-rrqc-395f)
- [SwiftNIO PR #2419 Add unprocessedBytes property on NIOSingleStepByteToMessageProcessor](https://github.com/apple/swift-nio/pull/2419)
- [PostgresNIO commit 2df54bc94607f44584ae6ffa74e3cd754fffafc7](https://github.com/vapor/postgres-nio/commit/2df54bc94607f44584ae6ffa74e3cd754fffafc7)
- [PostgresNIO 1.42.2 release](https://github.com/vapor/postgres-nio/releases/tag/1.14.2)
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'purl-type:swift', 'name': 'github.com/vapor/postgres-nio'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '1.14.2'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/vapor/postgres-nio/security/advisories/GHSA-9cfh-vx93-84vv'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-31136'}, {'type': 'WEB', 'url': 'https://github.com/apple/swift-nio/pull/2419'}, {'type': 'WEB', 'url': 'https://github.com/vapor/postgres-nio/commit/2df54bc94607f44584ae6ffa74e3cd754fffafc7'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-467w-rrqc-395f'}, {'type': 'ADVISORY', 'url': 'https://github.com/advisories/GHSA-735f-7qx4-jqq5'}, {'type': 'PACKAGE', 'url': 'https://github.com/vapor/postgres-nio'}, {'type': 'WEB', 'url': 'https://github.com/vapor/postgres-nio/releases/tag/1.14.2'}, {'type': 'WEB', 'url': 'https://www.postgresql.org/support/security/CVE-2021-23214/'}, {'type': 'WEB', 'url': 'https://www.postgresql.org/support/security/CVE-2021-23222/'}]
|
{'cwe_ids': ['CWE-522'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-05-10T19:20:16Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-gqxr-hvrw-6hfh
|
2023-05-17T03:37:48Z
|
2023-05-16T18:30:16Z
| null |
['CVE-2023-33000']
|
Jenkins NS-ND Integration Performance Publisher Plugin displays credentials without masking
|
Jenkins NS-ND Integration Performance Publisher Plugin stores credentials in job config.xml files on the Jenkins controller as part of its configuration.
While these credentials are stored encrypted on disk, in NS-ND Integration Performance Publisher Plugin 4.8.0.149 and earlier, the job configuration form does not mask these credentials, increasing the potential for attackers to observe and capture them.
NS-ND Integration Performance Publisher Plugin 4.11.0.48 masks credentials displayed on the configuration form.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Maven', 'name': 'io.jenkins.plugins:cavisson-ns-nd-integration'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.11.0.48'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-33000'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-2962'}]
|
{'cwe_ids': ['CWE-522'], 'severity': 'LOW', 'github_reviewed': True, 'github_reviewed_at': '2023-05-17T03:37:48Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-352v-hhmh-2w8h
|
2023-05-17T03:39:07Z
|
2023-05-16T18:30:16Z
| null |
['CVE-2023-2633']
|
Jenkins Code Dx Plugin displays API keys in plain text
|
Jenkins Code Dx Plugin 3.1.0 and earlier stores Code Dx server API keys unencrypted in job `config.xml` files on the Jenkins controller as part of its configuration.
These API keys can be viewed by users with Item/Extended Read permission or access to the Jenkins controller file system.
Additionally, the job configuration form does not mask these API keys, increasing the potential for attackers to observe and capture them.
Code Dx Plugin 4.0.0 no longer stores the API keys directly, instead accessing them through its newly added Credentials Plugin integration. Affected jobs need to be reconfigured.
|
[{'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.jenkins-ci.plugins:codedx'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '4.0.0'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-2633'}, {'type': 'WEB', 'url': 'https://www.jenkins.io/security/advisory/2023-05-16/#SECURITY-3146'}]
|
{'cwe_ids': ['CWE-256', 'CWE-522'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-17T03:39:07Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-549h-r7g9-2qpf
|
2023-05-30T20:07:50Z
|
2023-05-27T06:30:41Z
| null |
['CVE-2023-26127']
|
n158 vulnerable to Command Injection due to improper input sanitization in the 'module.exports' function
|
All versions of the package n158 are vulnerable to Command Injection due to improper input sanitization in the 'module.exports' function.
**Note:**
To execute the code snippet and potentially exploit the vulnerability, the attacker needs to have the ability to run Node.js code within the target environment. This typically requires some level of access to the system or application hosting the Node.js environment.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}]
|
[{'package': {'ecosystem': 'npm', 'name': 'n158'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'last_affected': '1.4.1'}]}]}]
|
[{'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-26127'}, {'type': 'PACKAGE', 'url': 'https://github.com/dsilva2401/n158'}, {'type': 'WEB', 'url': 'https://github.com/dsilva2401/n158/blob/master/src/cli/initProject.js#L8'}, {'type': 'WEB', 'url': 'https://security.snyk.io/vuln/SNYK-JS-N158-3183746'}]
|
{'cwe_ids': ['CWE-74', 'CWE-77'], 'severity': 'HIGH', 'github_reviewed': True, 'github_reviewed_at': '2023-05-30T20:07:50Z', 'nvd_published_at': None}
|
1.4.0
|
GHSA-92wq-q9pq-gw47
|
2023-05-25T19:07:49Z
|
2023-05-17T17:07:40Z
| null |
['CVE-2023-31135']
|
Dgraph Audit Log Encryption Vulnerability
|
### Impact
Existing Dgraph audit logs are vulnerable to brute force attacks due to nonce collisions. All audit logs generated by versions of Dgraph <v23.0.0 are affected.
### Patches
This issue was patched in https://github.com/dgraph-io/dgraph/pull/8323. Dgraph users should upgrade to v23.0.0.
### Workarounds
Store existing audit logs in a secure location. For extra security, encrypt using a tool like `gpg`.
### References
See https://github.com/dgraph-io/dgraph/pull/8323 for more context on the vulnerability.
|
[{'type': 'CVSS_V3', 'score': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}]
|
[{'package': {'ecosystem': 'Go', 'name': 'github.com/dgraph-io/dgraph'}, 'ranges': [{'type': 'ECOSYSTEM', 'events': [{'introduced': '0'}, {'fixed': '23.0.0'}]}]}]
|
[{'type': 'WEB', 'url': 'https://github.com/dgraph-io/dgraph/security/advisories/GHSA-92wq-q9pq-gw47'}, {'type': 'ADVISORY', 'url': 'https://nvd.nist.gov/vuln/detail/CVE-2023-31135'}, {'type': 'WEB', 'url': 'https://github.com/dgraph-io/dgraph/pull/8323'}, {'type': 'WEB', 'url': 'https://en.wikipedia.org/wiki/Cryptographic_nonce'}, {'type': 'PACKAGE', 'url': 'https://github.com/dgraph-io/dgraph'}, {'type': 'WEB', 'url': 'https://github.com/dgraph-io/dgraph/releases/tag/v23.0.0'}]
|
{'cwe_ids': ['CWE-326'], 'severity': 'MODERATE', 'github_reviewed': True, 'github_reviewed_at': '2023-05-17T17:07:40Z', 'nvd_published_at': None}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.