ecosystem
stringclasses 14
values | vuln_id
stringlengths 10
19
| summary
stringlengths 4
267
⌀ | details
stringlengths 9
13.5k
| aliases
stringlengths 17
144
⌀ | modified_date
stringdate 2010-05-27 05:47:00
2022-05-10 08:46:52
| published_date
stringdate 2005-12-31 05:00:00
2022-05-10 08:46:50
| severity
stringclasses 5
values | score
float64 0
10
⌀ | cwe_id
stringclasses 988
values | refs
stringlengths 30
17.7k
⌀ | introduced
stringlengths 75
4.26k
⌀ |
|---|---|---|---|---|---|---|---|---|---|---|---|
GHSA
|
GHSA-33rv-m2gp-mm2r
|
Prototype pollution in safe-flat
|
Prototype pollution vulnerability in 'safe-flat' versions 2.0.0 through 2.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.
|
{'CVE-2021-25927'}
|
2021-06-21T17:18:29Z
|
2021-06-21T17:18:29Z
|
CRITICAL
| 9.8
|
{'CWE-1321'}
|
{'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25927', 'https://github.com/jessie-codes/safe-flat/commit/4b9b7db976bba8c968354f4315f5f9c219b7cbf3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25927', 'https://github.com/advisories/GHSA-33rv-m2gp-mm2r'}
| null |
GHSA
|
GHSA-9pp4-8p8v-g78w
|
Data races in lever
|
An issue was discovered in the lever crate before 0.1.1 for Rust. AtomicBox<T> implements the Send and Sync traits for all types T. This allows non-Send types such as Rc and non-Sync types such as Cell to be used across thread boundaries which can trigger undefined behavior and memory corruption.
|
{'CVE-2020-36457'}
|
2021-08-25T20:57:26Z
|
2021-08-25T20:57:26Z
|
HIGH
| 8.1
|
{'CWE-362', 'CWE-77'}
|
{'https://rustsec.org/advisories/RUSTSEC-2020-0137.html', 'https://github.com/advisories/GHSA-9pp4-8p8v-g78w', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36457', 'https://github.com/vertexclique/lever/issues/15'}
| null |
GHSA
|
GHSA-535v-4x9q-446c
|
Moderate severity vulnerability that affects org.apache.hbase:hbase
|
In all previously released Apache HBase 2.x versions (2.0.0-2.0.4, 2.1.0-2.1.3), authorization was incorrectly applied to users of the HBase REST server. Requests sent to the HBase REST server were executed with the permissions of the REST server itself, not with the permissions of the end-user. This issue is only relevant when HBase is configured with Kerberos authentication, HBase authorization is enabled, and the REST server is configured with SPNEGO authentication. This issue does not extend beyond the HBase REST server.
|
{'CVE-2019-0212'}
|
2021-09-01T19:25:39Z
|
2019-04-02T15:47:00Z
|
HIGH
| 7.5
|
{'CWE-285'}
|
{'https://lists.apache.org/thread.html/66535e15007cda8f9308eec10e12ffe349e0b8b55e56ec6ee02b71d2@%3Cdev.hbase.apache.org%3E', 'https://github.com/advisories/GHSA-535v-4x9q-446c', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0212', 'http://www.securityfocus.com/bid/107624', 'http://www.openwall.com/lists/oss-security/2019/03/27/3'}
| null |
GHSA
|
GHSA-w4x5-jqq4-qc8x
|
SQL Injection in Cloud Native Computing Foundation Harbor
|
Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via project quotas in the VMware Harbor Container Registry for the Pivotal Platform.
|
{'CVE-2019-19026'}
|
2021-05-18T18:27:43Z
|
2021-05-18T18:27:43Z
|
MODERATE
| 4.9
|
{'CWE-89'}
|
{'https://github.com/advisories/GHSA-w4x5-jqq4-qc8x', 'https://github.com/goharbor/harbor/security/advisories/GHSA-rh89-vvrg-fg64', 'https://tanzu.vmware.com/security/cve-2019-19026', 'https://github.com/goharbor/harbor/security/advisories', 'https://nvd.nist.gov/vuln/detail/CVE-2019-19026'}
| null |
GHSA
|
GHSA-6226-h7ff-ch6c
|
Widget feature vulnerability allowing to execute JavaScript code using undo functionality
|
### Affected packages
The vulnerability has been discovered in [Widget](https://ckeditor.com/cke4/addon/clipboard) plugin if used alongside [Undo](https://ckeditor.com/cke4/addon/undo) feature.
### Impact
A potential vulnerability has been discovered in CKEditor 4 [Widget](https://ckeditor.com/cke4/addon/widget) package. The vulnerability allowed to abuse undo functionality using malformed widget HTML, which could result in executing JavaScript code. It affects all users using the CKEditor 4 plugins listed above at version >= 4.13.0.
### Patches
The problem has been recognized and patched. The fix will be available in version 4.16.2.
### For more information
Email us at security@cksource.com if you have any questions or comments about this advisory.
### Acknowledgements
The CKEditor 4 team would like to thank Anton Subbotin ([skavans](https://github.com/skavans)) for recognizing and reporting this vulnerability.
|
{'CVE-2021-32808'}
|
2022-02-08T21:01:57Z
|
2021-08-23T19:40:48Z
|
HIGH
| 7.6
|
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-32808', 'https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-6226-h7ff-ch6c', 'https://github.com/advisories/GHSA-6226-h7ff-ch6c', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/ckeditor/ckeditor4/releases/tag/4.16.2', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WAGNWHFIQAVCP537KFFS2A2GDG66J7XD/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UVOYN2WKDPLKCNILIGEZM236ABQASLGW/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NYA354LJP47KCVJMTUO77ZCX3ZK42G3T/', 'https://www.oracle.com/security-alerts/cpujan2022.html'}
| null |
GHSA
|
GHSA-8jf2-cq6v-w234
|
Malicious Package in uglyfi.js
|
Version 0.17.3 of `uglyfi.js` contains malicious code as a preinstall script. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When installed, the package downloads a file from a remote server, executes it and opens a backdoor.
## Recommendation
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer.
The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
| null |
2021-09-29T20:47:08Z
|
2020-09-03T21:10:53Z
|
CRITICAL
| 9.8
|
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1202', 'https://github.com/advisories/GHSA-8jf2-cq6v-w234'}
| null |
GHSA
|
GHSA-f5f7-6478-qm6p
|
Files or Directories Accessible to External Parties in kubernetes
|
A security issue was discovered in Kubernetes where a user may be able to create a container with subpath volume mounts to access files & directories outside of the volume, including on the host filesystem.
|
{'CVE-2021-25741'}
|
2021-11-01T17:32:28Z
|
2021-11-01T17:32:28Z
|
HIGH
| 8.1
|
{'CWE-552', 'CWE-20'}
|
{'https://github.com/kubernetes/kubernetes/issues/104980', 'https://github.com/advisories/GHSA-f5f7-6478-qm6p', 'https://groups.google.com/g/kubernetes-security-announce/c/nyfdhK24H7s', 'https://github.com/bottlerocket-os/bottlerocket/security/advisories/GHSA-f5f7-6478-qm6p', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25741', 'https://security.netapp.com/advisory/ntap-20211008-0006/'}
| null |
GHSA
|
GHSA-g4vj-x7v9-h82m
|
Overflow in libsecp256k1
|
An issue was discovered in the libsecp256k1 crate before 0.5.0 for Rust. It can verify an invalid signature because it allows the R or S parameter to be larger than the curve order, aka an overflow.
|
{'CVE-2021-38195'}
|
2021-08-25T20:56:03Z
|
2021-08-25T20:56:03Z
|
CRITICAL
| 9.8
|
{'CWE-347', 'CWE-190'}
|
{'https://github.com/paritytech/libsecp256k1/pull/67', 'https://rustsec.org/advisories/RUSTSEC-2021-0076.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-38195', 'https://github.com/advisories/GHSA-g4vj-x7v9-h82m'}
| null |
GHSA
|
GHSA-c9h6-xhg9-xxrv
|
Low severity vulnerability that affects org.apache.qpid:apache-qpid-broker-j
|
A Denial of Service vulnerability was found in Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 which allows an unauthenticated attacker to crash the broker instance by sending specially crafted commands using AMQP protocol versions below 1.0 (AMQP 0-8, 0-9, 0-91 and 0-10). Users of Apache Qpid Broker-J versions 6.0.0-7.0.6 (inclusive) and 7.1.0 utilizing AMQP protocols 0-8, 0-9, 0-91, 0-10 must upgrade to Qpid Broker-J versions 7.0.7 or 7.1.1 or later.
|
{'CVE-2019-0200'}
|
2021-07-27T16:05:21Z
|
2019-03-07T18:48:08Z
|
HIGH
| 7.5
|
{'CWE-20'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-0200', 'https://lists.apache.org/thread.html/ac79d48de37d42b64da50384dbe9c8a329c5f553dd12ef7c28a832de@%3Cusers.qpid.apache.org%3E', 'http://www.securityfocus.com/bid/107215', 'https://github.com/advisories/GHSA-c9h6-xhg9-xxrv'}
| null |
GHSA
|
GHSA-hhfg-6hfc-rvxm
|
Regular Expression Denial of Service in jsoneditor
|
JSON Editor is a web-based tool to view, edit, format, and validate JSON. It has various modes such as a tree editor, a code editor, and a plain text editor. The jsoneditor package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide a crafted element as input to the getInnerText function may cause an application to consume an excessive amount of CPU. Below pinned line using vulnerable regex.
|
{'CVE-2021-3822'}
|
2022-05-05T13:49:44Z
|
2021-09-29T17:15:55Z
|
MODERATE
| 5.3
|
{'CWE-400', 'CWE-697', 'CWE-1333'}
|
{'https://github.com/josdejong/jsoneditor/commit/092e386cf49f2a1450625617da8e0137ed067c3e', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3822', 'https://huntr.dev/bounties/1e3ed803-b7ed-42f1-a4ea-c4c75da9de73', 'https://github.com/advisories/GHSA-hhfg-6hfc-rvxm'}
| null |
GHSA
|
GHSA-p9m8-27x8-rg87
|
Critical vulnerability found in cron-utils
|
### Impact
A Template Injection was identified in cron-utils enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. Versions up to 9.1.2 are susceptible to this vulnerability. Please note, that only projects using the @Cron annotation to validate untrusted Cron expressions are affected.
### Patches
The issue was patched and a new version was released. Please upgrade to version 9.1.6.
### Workarounds
There are no known workarounds up to this moment.
### References
A description of the issue is provided in [issue 461](https://github.com/jmrozanec/cron-utils/issues/461)
### For more information
If you have any questions or comments about this advisory:
Open an issue in the [cron-utils Github repository](https://github.com/jmrozanec/cron-utils)
|
{'CVE-2021-41269'}
|
2022-04-19T19:03:15Z
|
2021-11-15T23:27:11Z
|
CRITICAL
| 10
|
{'CWE-94'}
|
{'https://github.com/jmrozanec/cron-utils/security/advisories/GHSA-p9m8-27x8-rg87', 'https://github.com/jmrozanec/cron-utils/issues/461', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41269', 'https://github.com/advisories/GHSA-p9m8-27x8-rg87', 'https://github.com/jmrozanec/cron-utils/commit/d6707503ec2f20947f79e38f861dba93b39df9da', 'https://github.com/jmrozanec/cron-utils/commit/cfd2880f80e62ea74b92fa83474c2aabdb9899da'}
| null |
GHSA
|
GHSA-f6pc-crhh-cp96
|
Privilege escalation in Presto
|
### Affected
This affects Presto server installations. This does NOT affect clients such as the CLI or JDBC driver.
### Impact
Authenticated users can bypass authorization checks by directly accessing internal APIs. This impacts Presto server installations with secure internal communication configured.
This does not affect installations that have not configured secure internal communication, as these installations are inherently insecure.
### Patches
This issue has been fixed starting with PrestoSQL version 337.
### Workarounds
This issue can be mitigated by blocking network access to internal APIs on the coordinator and workers.
### References
See the Presto documentation for [Secure Internal Communication](https://trino.io/docs/current/security/internal-communication.html).
### For more information
If you have any questions or comments about this advisory:
* Join the **#security** channel on [Slack](https://trino.io/slack.html).
* Contact the security team at [security@trino.io](mailto:security@trino.io).
|
{'CVE-2020-15087'}
|
2021-04-09T15:48:11Z
|
2020-06-30T16:33:23Z
|
HIGH
| 7.4
|
{'CWE-285'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-15087', 'https://github.com/trinodb/trino/security/advisories/GHSA-f6pc-crhh-cp96', 'https://prestosql.io/docs/current/release/release-337.html#security-changes', 'https://trino.io/docs/current/release/release-337.html#security-changes', 'https://github.com/prestosql/presto/security/advisories/GHSA-f6pc-crhh-cp96', 'https://github.com/advisories/GHSA-f6pc-crhh-cp96'}
| null |
GHSA
|
GHSA-hvgc-mggg-pxr2
|
Malicious Package in js-sha7
|
Version 0.8.0 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.
## Recommendation
Remove the package from your environment. Ensure no Ethereum funds were compromised.
| null |
2021-09-30T17:12:40Z
|
2020-09-03T23:02:33Z
|
CRITICAL
| 9.8
|
{'CWE-506'}
|
{'https://github.com/advisories/GHSA-hvgc-mggg-pxr2', 'https://www.npmjs.com/advisories/1284'}
| null |
GHSA
|
GHSA-gjwp-7v3g-99pj
|
Cross-site Request Forgery (CSRF) in joplin
|
The package joplin before 2.3.2 are vulnerable to Cross-site Request Forgery (CSRF) due to missing CSRF checks in various forms.
|
{'CVE-2021-23431'}
|
2021-09-02T17:09:05Z
|
2021-09-02T17:09:05Z
|
MODERATE
| 5.4
|
{'CWE-352'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-23431', 'https://github.com/advisories/GHSA-gjwp-7v3g-99pj', 'https://github.com/laurent22/joplin/commit/19b45de2981c09f6f387498ef96d32b4811eba5e', 'https://snyk.io/vuln/SNYK-JS-JOPLIN-1325537'}
| null |
GHSA
|
GHSA-4xg9-g7qj-jhg4
|
Malicious Package in comander
|
All versions of `comander` contains malicious code . The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. Upon require the package attempts to start a cryptocurrency miner using coin-hive.
## Recommendation
Remove the package from your environment and verify whether your system is running the cryptocurrency miner.
| null |
2021-09-29T20:33:41Z
|
2020-09-03T20:46:36Z
|
CRITICAL
| 9.8
|
{'CWE-506'}
|
{'https://github.com/advisories/GHSA-4xg9-g7qj-jhg4', 'https://www.npmjs.com/advisories/1193'}
| null |
GHSA
|
GHSA-5qjq-69w6-fg57
|
XSS vulnerability with translator
|
Flarum's translation system allowed for string inputs to be converted into HTML DOM nodes when rendered. This change was made after v0.1.0-beta.16 (our last beta before v1.0.0) and was not noticed or documented.
This allowed for any user to type malicious HTML markup within certain user input fields and have this execute on client browsers. The example which led to the discovery of this vulnerability was in the forum search box. Entering faux-malicious HTML markup, such as <script>alert('test')</script> resulted in an alert box appearing on the forum. This attack could also be modified to perform AJAX requests on behalf of a user, possibly deleting discussions, modifying their settings or profile, or even modifying settings on the Admin panel if the attack was targetted towards a privileged user.
### Impact
All Flarum communities that run flarum v1.0.0 or v1.0.1 are impacted.
### Patches
The vulnerability has been fixed and published as flarum/core v1.0.2. All communities running Flarum v1.0 have to upgrade as soon as possible to v1.0.2 using:
```
composer update --prefer-dist --no-dev -a -W
```
You can then confirm you run the latest version using:
```
composer show flarum/core
```
### Workarounds
__None.__
### For more information
For any questions or comments on this vulnerability please visit https://discuss.flarum.org/d/27558.
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, and we will address it promptly.
|
{'CVE-2021-32671'}
|
2022-04-19T19:02:59Z
|
2021-06-07T21:48:17Z
|
CRITICAL
| 10
|
{'CWE-79'}
|
{'https://github.com/advisories/GHSA-5qjq-69w6-fg57', 'https://github.com/flarum/core/security/advisories/GHSA-5qjq-69w6-fg57', 'https://github.com/flarum/core/commit/440bed81b8019dff00642c8f493b4909d505a28a', 'https://packagist.org/packages/flarum/core', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32671'}
| null |
GHSA
|
GHSA-3837-87vh-xq3w
|
Data race in v9
|
v9 is a slim data engine for Data Oriented Design. An issue was discovered in the v9 crate through 2020-12-18 for Rust. There is an unconditional implementation of Sync for SyncRef<T>.
|
{'CVE-2020-36447'}
|
2022-05-04T03:17:00Z
|
2021-08-25T20:57:07Z
|
HIGH
| 8.1
|
{'CWE-77'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36447', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/v9/RUSTSEC-2020-0127.md', 'https://github.com/advisories/GHSA-3837-87vh-xq3w', 'https://github.com/purpleposeidon/v9/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2020-0127.html'}
| null |
GHSA
|
GHSA-mgjw-2wrp-r535
|
Remote code execution in xwiki-platform
|
### Impact
It's possible for an unprivileged user to perform a remote code execution by injecting a groovy script in her own profile and by calling the Reset password feature since the feature is performing a save of the user profile with programming rights in the impacted versions of XWiki.
### Patches
The problem has been patched in XWiki 13.1RC1 with a complete refactoring of the Reset password feature.
### Workarounds
There's different possible workarounds, all consisting in modifying the XWiki/ResetPassword page.
- the Reset password feature can be entirely disabled by deleting the XWiki/ResetPassword page
- the script in XWiki/ResetPassword can also be modified or removed: an administrator can replace it with a simple email contact to ask an administrator to reset the password.
### References
https://jira.xwiki.org/browse/XWIKI-16661
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Jira](https://jira.xwiki.org)
* Email us at [Security mailing-list](mailto:security@xwiki.org)
|
{'CVE-2022-23616'}
|
2022-02-11T15:01:24Z
|
2022-02-09T21:32:10Z
|
HIGH
| 8.8
|
{'CWE-74'}
|
{'https://jira.xwiki.org/browse/XWIKI-16661', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23616', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-mgjw-2wrp-r535', 'https://github.com/advisories/GHSA-mgjw-2wrp-r535'}
| null |
GHSA
|
GHSA-4r62-v4vq-hr96
|
Regular Expression Denial of Service (REDoS) in Marked
|
### Impact
_What kind of vulnerability is it? Who is impacted?_
[Regular expression Denial of Service](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS)
A Denial of Service attack can affect anyone who runs user generated code through `marked`.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
patched in v2.0.0
### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
None.
### References
_Are there any links users can visit to find out more?_
https://github.com/markedjs/marked/issues/1927
https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [marked](https://github.com/markedjs/marked/issues)
|
{'CVE-2021-21306'}
|
2022-04-19T19:02:46Z
|
2021-02-08T21:17:58Z
|
MODERATE
| 5.3
|
{'CWE-400'}
|
{'https://www.npmjs.com/package/marked', 'https://github.com/markedjs/marked/issues/1927', 'https://github.com/markedjs/marked/pull/1864', 'https://github.com/advisories/GHSA-4r62-v4vq-hr96', 'https://github.com/markedjs/marked/commit/7293251c438e3ee968970f7609f1a27f9007bccd', 'https://github.com/markedjs/marked/security/advisories/GHSA-4r62-v4vq-hr96', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21306'}
| null |
GHSA
|
GHSA-4p55-xj37-fx7g
|
Improper Authorization in Strapi
|
In Strapi before 3.2.5, there is no admin::hasPermissions restriction for CTB (aka content-type-builder) routes.
|
{'CVE-2020-27665'}
|
2021-01-08T21:21:57Z
|
2020-10-29T18:29:31Z
|
MODERATE
| 0
|
{'CWE-276'}
|
{'https://snyk.io/vuln/SNYK-JS-STRAPIPLUGINCONTENTTYPEBUILDER-1021616', 'https://github.com/strapi/strapi/commit/3cdd73987950d5c7976701047b38203e902007bb', 'https://github.com/advisories/GHSA-4p55-xj37-fx7g', 'https://github.com/strapi/strapi/pull/8439', 'https://github.com/strapi/strapi/releases/tag/v3.2.5', 'https://nvd.nist.gov/vuln/detail/CVE-2020-27665'}
| null |
GHSA
|
GHSA-28xh-wpgr-7fm8
|
Command Injection in open
|
Versions of `open` before 6.0.0 are vulnerable to command injection when unsanitized user input is passed in.
The package does come with the following warning in the readme:
```
The same care should be taken when calling open as if you were calling child_process.exec directly. If it is an executable it will run in a new shell.
```
## Recommendation
`open` is now the deprecated `opn` package. Upgrading to the latest version is likely have unwanted effects since it now has a very different API but will prevent this vulnerability.
| null |
2021-08-17T13:17:37Z
|
2019-06-20T15:35:49Z
|
CRITICAL
| 0
|
{'CWE-77'}
|
{'https://github.com/pwnall/node-open/issues/68', 'https://hackerone.com/reports/319473', 'https://github.com/advisories/GHSA-28xh-wpgr-7fm8', 'https://www.npmjs.com/advisories/663', 'https://nodesecurity.io/advisories/663', 'https://github.com/pwnall/node-open/issues/69'}
| null |
GHSA
|
GHSA-fvq6-55gv-jx9f
|
SQL Injection in mysql
|
Versions of `mysql` prior to 2.0.0-alpha8 are affected by a SQL Injection vulnerability in the `mysql.escape()` function, which does not properly escape object keys.
## Recommendation
Update to version 2.0.0-alpha8 or later.
|
{'CVE-2015-9244'}
|
2021-01-07T23:35:25Z
|
2020-09-01T15:21:05Z
|
MODERATE
| 0
|
{'CWE-89'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2015-9244', 'https://nodesecurity.io/advisories/66', 'https://github.com/advisories/GHSA-fvq6-55gv-jx9f', 'https://www.npmjs.com/advisories/66', 'https://github.com/felixge/node-mysql/issues/342'}
| null |
GHSA
|
GHSA-gc45-j3m5-8qfq
|
Server-Side Request Forgery in Feehi CMS
|
Feehi CMS 2.1.1 is affected by a Server-side request forgery (SSRF) vulnerability. When the user modifies the HTTP Referer header to any url, the server can make a request to it.
|
{'CVE-2021-30108'}
|
2021-06-08T20:12:32Z
|
2021-06-08T20:12:32Z
|
CRITICAL
| 9.1
|
{'CWE-918'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-30108', 'https://github.com/liufee/cms/issues/57', 'https://github.com/advisories/GHSA-gc45-j3m5-8qfq'}
| null |
GHSA
|
GHSA-6c3j-c64m-qhgq
|
XSS in jQuery as used in Drupal, Backdrop CMS, and other products
|
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
|
{'CVE-2019-11358'}
|
2022-04-07T15:12:22Z
|
2019-04-26T16:29:11Z
|
MODERATE
| 6.1
|
{'CWE-79', 'CWE-1321'}
|
{'http://packetstormsecurity.com/files/156743/OctoberCMS-Insecure-Dependencies.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'http://www.securityfocus.com/bid/108023', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RLXRX23725JL366CNZGJZ7AQQB7LHQ6F/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4UOAZIFCSZ3ENEFOR5IXX6NFAD3HV7FA/', 'http://seclists.org/fulldisclosure/2019/May/10', 'https://security.netapp.com/advisory/ntap-20190919-0001/', 'https://lists.apache.org/thread.html/r38f0d1aa3c923c22977fe7376508f030f22e22c1379fbb155bf29766@%3Cdev.syncope.apache.org%3E', 'https://www.tenable.com/security/tns-2019-08', 'https://lists.apache.org/thread.html/r2041a75d3fc09dec55adfd95d598b38d22715303f65c997c054844c9@%3Cissues.flink.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/05/msg00029.html', 'http://seclists.org/fulldisclosure/2019/May/11', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://lists.apache.org/thread.html/88fb0362fd40e5b605ea8149f63241537b8b6fb5bfa315391fc5cbb7@%3Ccommits.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/ba79cf1658741e9f146e4c59b50aee56656ea95d841d358d006c18b6@%3Ccommits.roller.apache.org%3E', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://github.com/jquery/jquery/pull/4333', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'http://packetstormsecurity.com/files/153237/RetireJS-CORS-Issue-Script-Execution.html', 'https://lists.apache.org/thread.html/rac25da84ecdcd36f6de5ad0d255f4e967209bbbebddb285e231da37d@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/08720ef215ee7ab3386c05a1a90a7d1c852bf0706f176a7816bf65fc@%3Ccommits.airflow.apache.org%3E', 'https://www.debian.org/security/2019/dsa-4434', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://backdropcms.org/security/backdrop-sa-core-2019-009', 'https://access.redhat.com/errata/RHBA-2019:1570', 'http://www.openwall.com/lists/oss-security/2019/06/03/2', 'https://www.privacy-wise.com/mitigating-cve-2019-11358-in-old-versions-of-jquery/', 'https://github.com/advisories/GHSA-6c3j-c64m-qhgq', 'https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/', 'http://seclists.org/fulldisclosure/2019/May/13', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00024.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5IABSKTYZ5JUGL735UKGXL5YPRYOPUYI/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KYH3OAGR2RTCHRA5NOKX2TES7SNQMWGO/', 'https://seclists.org/bugtraq/2019/Apr/32', 'https://lists.apache.org/thread.html/r41b5bfe009c845f67d4f68948cc9419ac2d62e287804aafd72892b08@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r7e8ebccb7c022e41295f6fdb7b971209b83702339f872ddd8cf8bf73@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/r7d64895cc4dff84d0becfc572b20c0e4bf9bfa7b10c6f5f73e783734@%3Cdev.storm.apache.org%3E', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html', 'https://lists.apache.org/thread.html/b736d0784cf02f5a30fbb4c5902762a15ad6d47e17e2c5a17b7d6205@%3Ccommits.airflow.apache.org%3E', 'https://seclists.org/bugtraq/2019/Jun/12', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QV3PKZC3PQCO3273HAT76PAQZFBEO4KP/', 'https://lists.apache.org/thread.html/6097cdbd6f0a337bedd9bb5cc441b2d525ff002a96531de367e4259f@%3Ccommits.airflow.apache.org%3E', 'https://snyk.io/vuln/SNYK-JS-JQUERY-174006', 'https://www.synology.com/security/advisory/Synology_SA_19_19', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WZW27UCJ5CYFL4KFFFMYMIBNMIU2ALG5/', 'https://lists.debian.org/debian-lts-announce/2019/05/msg00006.html', 'https://www.debian.org/security/2019/dsa-4460', 'https://lists.apache.org/thread.html/5928aa293e39d248266472210c50f176cac1535220f2486e6a7fa844@%3Ccommits.airflow.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:3024', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html', 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44601', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'http://packetstormsecurity.com/files/152787/dotCMS-5.1.1-Vulnerable-Dependencies.html', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11358', 'https://www.drupal.org/sa-core-2019-006', 'https://www.tenable.com/security/tns-2020-02', 'https://access.redhat.com/errata/RHSA-2019:1456', 'https://access.redhat.com/errata/RHSA-2019:3023', 'https://lists.apache.org/thread.html/r7aac081cbddb6baa24b75e74abf0929bf309b176755a53e3ed810355@%3Cdev.flink.apache.org%3E', 'https://github.com/jquery/jquery/commit/753d591aea698e57d6db58c9f722cd0808619b1b', 'https://seclists.org/bugtraq/2019/May/18', 'https://access.redhat.com/errata/RHSA-2019:2587', 'https://lists.apache.org/thread.html/r2baacab6e0acb5a2092eb46ae04fd6c3e8277b4fd79b1ffb7f3254fa@%3Cissues.flink.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'}
| null |
GHSA
|
GHSA-77rv-6vfw-x4gc
|
Critical severity vulnerability that affects org.springframework.security.oauth:spring-security-oauth and org.springframework.security.oauth:spring-security-oauth2
|
Spring Security OAuth, versions 2.3 prior to 2.3.5, and 2.2 prior to 2.2.4, and 2.1 prior to 2.1.4, and 2.0 prior to 2.0.17, and older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code.
A malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the "redirect_uri" parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.
This vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and uses the DefaultRedirectResolver in the AuthorizationEndpoint.
This vulnerability does not expose applications that: Act in the role of an Authorization Server and uses a different RedirectResolver implementation other than DefaultRedirectResolver, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).
|
{'CVE-2019-3778'}
|
2021-01-22T20:49:23Z
|
2019-03-14T15:39:30Z
|
CRITICAL
| 0
|
{'CWE-601'}
|
{'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-3778', 'https://github.com/advisories/GHSA-77rv-6vfw-x4gc', 'https://pivotal.io/security/cve-2019-3778', 'http://www.securityfocus.com/bid/107153', 'http://packetstormsecurity.com/files/153299/Spring-Security-OAuth-2.3-Open-Redirection.html'}
| null |
GHSA
|
GHSA-43jf-985q-588j
|
Multiple `CHECK`-fails in `function.cc` in TensowFlow
|
### Impact
A malicious user can cause a denial of service by altering a `SavedModel` such that [assertions in `function.cc`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/function.cc) would be falsified and crash the Python interpreter.
### Patches
We have patched the issue in GitHub commits [dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2](https://github.com/tensorflow/tensorflow/commit/dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2) and [3d89911481ba6ebe8c88c1c0b595412121e6c645](https://github.com/tensorflow/tensorflow/commit/3d89911481ba6ebe8c88c1c0b595412121e6c645).
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
|
{'CVE-2022-23586'}
|
2022-02-11T20:31:30Z
|
2022-02-09T23:27:08Z
|
MODERATE
| 6.5
|
{'CWE-617'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-23586', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-43jf-985q-588j', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/function.cc', 'https://github.com/tensorflow/tensorflow/commit/3d89911481ba6ebe8c88c1c0b595412121e6c645', 'https://github.com/tensorflow/tensorflow/commit/dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2', 'https://github.com/advisories/GHSA-43jf-985q-588j'}
| null |
GHSA
|
GHSA-x5ph-4fr4-g7fw
|
Downloads Resources over HTTP in galenframework-cli
|
Affected versions of `galenframework-cli` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `galenframework-cli`.
## Recommendation
Update to version 2.3.1 or later.
|
{'CVE-2016-10560'}
|
2021-01-08T00:47:47Z
|
2019-02-18T23:54:21Z
|
HIGH
| 0
|
{'CWE-311'}
|
{'https://www.npmjs.com/advisories/170', 'https://nodesecurity.io/advisories/170', 'https://github.com/advisories/GHSA-x5ph-4fr4-g7fw', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10560'}
| null |
GHSA
|
GHSA-x3w4-mrmv-cw2x
|
Malicious Package in buffev-xor
|
Version 2.0.2 contained malicious code. The package targeted the Ethereum cryptocurrency and performed transactions to wallets not controlled by the user.
## Recommendation
Remove the package from your environment. Ensure no Ethereum funds were compromised.
| null |
2021-09-29T21:26:20Z
|
2020-09-03T22:19:44Z
|
CRITICAL
| 9.8
|
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1258', 'https://github.com/advisories/GHSA-x3w4-mrmv-cw2x'}
| null |
GHSA
|
GHSA-2v5f-23xc-v9qr
|
Cross-site scripting
|
The npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.
|
{'CVE-2021-3377'}
|
2021-03-11T22:50:39Z
|
2021-03-11T22:50:39Z
|
MODERATE
| 0
|
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-3377', 'https://github.com/drudru/ansi_up/commit/c8c726ed1db979bae4f257b7fa41775155ba2e27', 'https://doyensec.com/resources/Doyensec_Advisory_ansi_up4_XSS.pdf', 'https://github.com/advisories/GHSA-2v5f-23xc-v9qr'}
| null |
GHSA
|
GHSA-cqr7-78pj-3g7j
|
File Descriptor Leak Can Cause DoS Vulnerability in hapi
|
Versions 2.0.x and 2.1.x of hapi are vulnerable to a denial of service attack via a file descriptor leak.
When triggered repeatedly, this leak will cause the server to run out of file descriptors and the node process to die. The effort required to take down a server depends on the process file descriptor limit. No other side effects or exploits have been identified.
## Recommendation
- Please upgrade to version 2.2.x or above as soon as possible.
|
{'CVE-2014-3742'}
|
2021-09-09T20:31:03Z
|
2017-10-24T18:33:36Z
|
HIGH
| 0
| null |
{'http://www.openwall.com/lists/oss-security/2014/05/15/2', 'https://nodesecurity.io/advisories/hapi_File_descriptor_leak_DoS_vulnerability', 'https://www.npmjs.com/advisories/11', 'https://github.com/spumko/hapi/issues/1427', 'https://github.com/advisories/GHSA-cqr7-78pj-3g7j', 'https://nvd.nist.gov/vuln/detail/CVE-2014-3742', 'http://www.openwall.com/lists/oss-security/2014/05/13/1'}
| null |
GHSA
|
GHSA-r6v3-hpxj-r8rv
|
Code Injection in PyXDG
|
A code injection issue was discovered in PyXDG before 0.26 via crafted Python code in a Category element of a Menu XML document in a .menu file. XDG_CONFIG_DIRS must be set up to trigger xdg.Menu.parse parsing within the directory containing this file. This is due to a lack of sanitization in xdg/Menu.py before an eval call.
|
{'CVE-2019-12761'}
|
2021-08-31T21:17:12Z
|
2019-06-07T20:56:27Z
|
HIGH
| 7.5
|
{'CWE-94'}
|
{'https://snyk.io/vuln/SNYK-PYTHON-PYXDG-174562', 'https://lists.debian.org/debian-lts-announce/2019/06/msg00006.html', 'https://lists.debian.org/debian-lts-announce/2021/08/msg00003.html', 'https://nvd.nist.gov/vuln/detail/CVE-2019-12761', 'https://gist.github.com/dhondta/b45cd41f4186110a354dc7272916feba', 'https://github.com/advisories/GHSA-r6v3-hpxj-r8rv'}
| null |
GHSA
|
GHSA-xc6g-ggrc-qq4r
|
Cross-Site Scripting in sanitize-html
|
Affected versions of `sanitize-html` are vulnerable to cross-site scripting when allowedTags includes at least one `nonTextTag`.
## Proof of Concept
```
var sanitizeHtml = require('sanitize-html');
var dirty = '!<textarea></textarea><svg/onload=prompt`xs`></textarea>!';
var clean = sanitizeHtml(dirty, {
allowedTags: [ 'textarea' ]
});
console.log(clean);
// !<textarea></textarea><svg/onload=prompt`xs`></textarea>!
```
## Recommendation
Update to version 1.11.4 or later.
|
{'CVE-2017-16016'}
|
2021-01-08T21:15:03Z
|
2018-11-09T17:47:23Z
|
MODERATE
| 0
|
{'CWE-79'}
|
{'https://nodesecurity.io/advisories/154', 'https://github.com/punkave/sanitize-html/issues/100', 'https://npmjs.com/package/sanitize-html#discarding-the-entire-contents-of-a-disallowed-tag', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16016', 'https://www.npmjs.com/advisories/154', 'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403)))', 'https://github.com/advisories/GHSA-xc6g-ggrc-qq4r', 'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403'}
| null |
GHSA
|
GHSA-5mhv-9qw8-j63g
|
Hijacked Environment Variables in mssql.js
|
The `mssql.js` package is a piece of malware that steals environment variables and sends them to attacker controlled locations.
All versions have been unpublished from the npm registry.
## Recommendation
As this package is malware, if you find it installed in your environment, the real security concern is determining how it got there.
If you have found this installed in your environment, you should:
1. Delete the package
2. Clear your npm cache
3. Ensure it is not present in any other package.json files on your system
4. Regenerate your registry credentials, tokens, and any other sensitive credentials that may have been present in your environment variables.
Additionally, any service which may have been exposed via credentials in your environment variables, such as a database, should be reviewed for indicators of compromise as well.
|
{'CVE-2017-16056'}
|
2021-01-08T19:49:01Z
|
2018-11-09T17:43:03Z
|
MODERATE
| 0
|
{'CWE-506'}
|
{'https://github.com/advisories/GHSA-5mhv-9qw8-j63g', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16056', 'https://www.npmjs.com/advisories/485', 'https://nodesecurity.io/advisories/485'}
| null |
GHSA
|
GHSA-2h63-qp69-fwvw
|
Server-side request forgery (SSRF) in Apache Batik
|
Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.
|
{'CVE-2020-11987'}
|
2022-02-08T21:33:50Z
|
2022-01-06T20:35:54Z
|
HIGH
| 8.2
|
{'CWE-20', 'CWE-918'}
|
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JEDID4DAVPECE6O4QQCSIS75BLLBUUAM/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/W7EAYO5XIHD6OIEA3HPK64UDDBSLNAC5/', 'https://lists.apache.org/thread.html/r588d05a0790b40a0eb81088252e1e8c1efb99706631421f17038eb05@%3Cdev.poi.apache.org%3E', 'https://lists.apache.org/thread.html/r2877ae10e8be56a3c52d03e373512ddd32f16b863f24c2e22f5a5ba2@%3Cdev.poi.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11987', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/advisories/GHSA-2h63-qp69-fwvw', 'https://xmlgraphics.apache.org/security.html', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/apache/xmlgraphics-batik/commit/0ef5b661a1f77772d1110877ea9e0287987098f6', 'https://www.oracle.com//security-alerts/cpujul2021.html'}
| null |
GHSA
|
GHSA-wj6h-7chw-x4h2
|
Command injection in get-git-data
|
get-git-data through 1.3.1 is vulnerable to Command Injection. It is possible to inject arbitrary commands as part of the arguments provided to get-git-data.
|
{'CVE-2020-7619'}
|
2021-07-28T21:53:40Z
|
2021-05-10T15:59:14Z
|
CRITICAL
| 9.8
|
{'CWE-78'}
|
{'https://github.com/advisories/GHSA-wj6h-7chw-x4h2', 'https://github.com/chardos/get-git-data/blob/master/index.js#L7,', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7619', 'https://snyk.io/vuln/SNYK-JS-GETGITDATA-564222'}
| null |
GHSA
|
GHSA-j6wp-3859-vxfg
|
OIDC claims not updated from Identity Provider in Pomerium
|
### Impact
Changes to the OIDC claims of a user after initial login are not reflected in policy evaluation when using [`allowed_idp_claims`](https://www.pomerium.com/reference/#allowed-idp-claims) as part of policy. If using `allowed_idp_claims` and a user's claims are changed, Pomerium can make incorrect authorization decisions.
### Patches
v0.15.6
### Workarounds
- Clear data on `databroker` service by clearing redis or restarting the in-memory databroker to force claims to be updated
### References
https://github.com/pomerium/pomerium/pull/2724
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Pomerium](https://github.com/pomerium/pomerium)
* Email us at [security@pomerium.com](mailto:security@pomerium.com)
|
{'CVE-2021-41230'}
|
2021-11-10T16:52:24Z
|
2021-11-10T16:52:24Z
|
MODERATE
| 5.3
|
{'CWE-863'}
|
{'https://github.com/advisories/GHSA-j6wp-3859-vxfg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41230', 'https://github.com/pomerium/pomerium/pull/2724', 'https://github.com/pomerium/pomerium/security/advisories/GHSA-j6wp-3859-vxfg'}
| null |
GHSA
|
GHSA-v89p-5hr2-4rh4
|
Out-of-bounds write
|
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196.
|
{'CVE-2019-1197'}
|
2021-03-29T20:56:15Z
|
2021-03-29T20:56:15Z
|
HIGH
| 7.5
|
{'CWE-787'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-1197', 'https://github.com/advisories/GHSA-v89p-5hr2-4rh4', 'https://github.com/chakra-core/ChakraCore/commit/bf52b6cfa96d6395046d0aaf87396cd7ca13f6cb', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1197'}
| null |
GHSA
|
GHSA-46rx-6jg9-4fh8
|
Cross-site Scripting in LibreNMS
|
LibreNMS through 21.10.2 allows XSS via a widget title.
|
{'CVE-2021-43324'}
|
2021-11-08T17:59:15Z
|
2021-11-08T17:59:15Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-43324', 'https://github.com/advisories/GHSA-46rx-6jg9-4fh8', 'https://github.com/librenms/librenms/commit/99d2462b80435b91a35236639b909eebee432126'}
| null |
GHSA
|
GHSA-5wjf-62hw-q78r
|
Excessive CPU usage
|
Envoy, which Pomerium is based on, incorrectly handles resetting of HTTP/2 streams with excessive complexity. This can lead to high CPU utilization when a large number of streams are reset.
### Impact
This can result in a DoS condition.
### Patches
Pomerium versions 0.14.8 and 0.15.1 contain an upgraded envoy binary with this vulnerability patched.
### Workarounds
N/A
### References
[envoy GSA](https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc)
[envoy CVE](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32778)
[envoy announcement](https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [pomerium/pomerium](https://github.com/pomerium/pomerium/issues)
* Email us at [security@pomerium.com](mailto:security@pomerium.com)
|
{'CVE-2021-39204'}
|
2021-09-13T19:57:44Z
|
2021-09-10T17:54:13Z
|
HIGH
| 7.5
|
{'CWE-834'}
|
{'https://github.com/pomerium/pomerium/security/advisories/GHSA-5wjf-62hw-q78r', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39204', 'https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ', 'https://github.com/advisories/GHSA-5wjf-62hw-q78r', 'https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc'}
| null |
GHSA
|
GHSA-rmj8-8hhh-gv5h
|
Information Exposure when using Puma with Rails
|
### Impact
Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly.
From Rails:
> Under certain circumstances response bodies will not be closed, for example a bug in a webserver[1] or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes.
The combination of these two behaviors (Puma not closing the body + Rails' Executor implementation) causes information leakage.
### Patches
This problem is fixed in Puma versions 5.6.2 and 4.3.11.
This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
See:
https://github.com/advisories/GHSA-wh98-p28r-vrc9
for details about the rails vulnerability
Upgrading to a patched Rails _or_ Puma version fixes the vulnerability.
### Workarounds
Upgrade to Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2.
The [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1) includes a middleware that can be used instead.
### References
* Rails CVE: [CVE-2022-23633](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1)
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [puma](https://github.com/puma/puma)
* See our [security policy](https://github.com/puma/puma/security/policy)
|
{'CVE-2022-23634'}
|
2022-04-19T19:03:23Z
|
2022-02-11T21:33:23Z
|
HIGH
| 8
|
{'CWE-200'}
|
{'https://github.com/advisories/GHSA-wh98-p28r-vrc9', 'https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1', 'https://github.com/advisories/GHSA-rmj8-8hhh-gv5h', 'https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23634', 'https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h'}
| null |
GHSA
|
GHSA-gcx5-3p5f-f8vp
|
Prototype Pollution in jquery.cookie
|
jQuery Cookie 1.4.1 is affected by prototype pollution, which can lead to DOM cross-site scripting (XSS).
|
{'CVE-2022-23395'}
|
2022-03-29T22:13:34Z
|
2022-03-03T00:00:51Z
|
MODERATE
| 6.1
|
{'CWE-1321'}
|
{'https://security.netapp.com/advisory/ntap-20220325-0008/', 'https://github.com/advisories/GHSA-gcx5-3p5f-f8vp', 'https://snyk.io/test/npm/jquery.cookie/1.4.1?tab=issues', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23395'}
| null |
GHSA
|
GHSA-gh78-48h3-frjq
|
Improper exception handling in Aedes
|
An issue was discovered in MoscaJS Aedes 0.42.0 and fixed in 0.42.1. lib/write.js does not properly consider exceptions during the writing of an invalid packet to a stream.
|
{'CVE-2020-13410'}
|
2021-05-06T18:10:46Z
|
2021-05-06T18:10:46Z
|
HIGH
| 7.5
|
{'CWE-755'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-13410', 'https://github.com/moscajs/aedes/pull/493', 'https://github.com/moscajs/aedes/commit/8d34ee5819cfc983d57e49b45d8c5ef70a76d79b', 'https://github.com/advisories/GHSA-gh78-48h3-frjq', 'https://payatu.com/advisory/dos-in-aedes-mqtt-broker'}
| null |
GHSA
|
GHSA-2r6j-862c-m2v2
|
Unrestricted File Upload in Form Framework
|
### Problem
Due to the lack of ensuring file extensions belong to configured allowed mime-types, attackers can upload arbitrary data with arbitrary file extensions - however, default _fileDenyPattern_ successfully blocked files like _.htaccess_ or _malicious.php_.
TYPO3 Extbase extensions, which implement a file upload and do not implement a custom _TypeConverter_ to transform uploaded files into _FileReference_ domain model objects are affected by the vulnerability as well, since the _UploadedFileReferenceConverter_ of _ext:form_ handles the file upload and will accept files of any mime-type which are persisted to the default location.
In any way, uploaded files are placed in the default location _/fileadmin/user_upload/_, in most scenarios keeping the submitted filename - which allows attackers to directly reference files, or even correctly guess filenames used by other individuals, disclosing this information.
No authentication is required to exploit this vulnerability.
### Solution
Update to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.
Type converter _UploadedFileReferenceConverter_ is not registered globally anymore and just handles uploaded files within the scope of the Form Framework. Guessable storage location has changed from _/fileadmin/user_upload/form\_\<random-hash\>/_ to _/fileadmin/form_uploads/<random-40-bit>_. Allowed mime-types must match expected file extensions (e.g. _application/pdf_ must be _.pdf_, and cannot be _.html_).
Extbase extensions, who rely on the global availability of the _UploadedFileReferenceConverter_ must now implement a custom _TypeConverter_ to handle file uploads or explicitly implement the ext:form _UploadedFileReferenceConverter_ with appropriate setting for accepted mime-types.
### Credits
Thanks to Sebastian Michaelsen, Marc Lindemann, Oliver Eglseder, Markus Volkmer, Jakob Kunzmann, Johannes Regner, Richie Lee who reported this issue, and to TYPO3 core & security team members Oliver Hader & Benni Mack, as well as TYPO3 contributor Ralf Zimmermann who fixed the issue.
### References
* [TYPO3-CORE-SA-2021-002](https://typo3.org/security/advisory/typo3-core-sa-2021-002)
|
{'CVE-2021-21355'}
|
2022-04-19T19:02:51Z
|
2021-03-23T01:53:52Z
|
HIGH
| 8
|
{'CWE-552', 'CWE-434'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-21355', 'https://typo3.org/security/advisory/typo3-core-sa-2021-002', 'https://github.com/advisories/GHSA-2r6j-862c-m2v2', 'https://github.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-2r6j-862c-m2v2', 'https://packagist.org/packages/typo3/cms-form'}
| null |
GHSA
|
GHSA-vhgr-gfx3-fg37
|
Unrestricted Upload of File with Dangerous Type in WPanel 4
|
Multiple Remote Code Execution (RCE) vulnerabilities exist in WPanel 4 4.3.1 and below via a malicious PHP file upload to (1) Dashboard's Avatar image, (2) Posts Folder image, (3) Pages Folder image and (4) Gallery Folder image.
|
{'CVE-2021-34257'}
|
2022-04-12T21:58:09Z
|
2022-04-01T00:00:41Z
|
HIGH
| 8.8
|
{'CWE-434'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-34257', 'https://latestpcsolution.wordpress.com/2021/06/05/wpanel4-cms-authenticated-rce/', 'https://github.com/Sentinal920/WPanel4-Authenticated-RCE', 'https://github.com/advisories/GHSA-vhgr-gfx3-fg37'}
| null |
GHSA
|
GHSA-4v9q-hm2p-68c4
|
Spoofing attack due to unvalidated KDC in node-krb5
|
Affected versions of `node-krb5` do not validate the KDC prior to authenticating, which might allow an attacker with network access and enough time to spoof the KDC and impersonate a valid user without knowing their credentials.
## Recommendation
It appears that this will remain unfixed indefinitely, as the Github issue for this vulnerability has been open since 2015, with no work on it since then.
At this time, the best available mitigation is to use an alternative module that is actively maintained and provides similar functionality. There are [multiple modules fitting this criteria available on npm.](https://www.npmjs.com/search?q=kerberos).
|
{'CVE-2016-1000238'}
|
2021-09-23T21:35:23Z
|
2020-09-01T15:57:01Z
|
MODERATE
| 0
| null |
{'https://github.com/advisories/GHSA-4v9q-hm2p-68c4', 'https://nvd.nist.gov/vuln/detail/CVE-2016-1000238', 'https://www.npmjs.com/advisories/136', 'https://github.com/qesuto/node-krb5/issues/13', 'http://archive.hack.lu/2010/Bouillon-Stealing-credentials-for-impersonation.pdf'}
| null |
GHSA
|
GHSA-8j8c-7jfh-h6hx
|
Code Injection in js-yaml
|
Versions of `js-yaml` prior to 3.13.1 are vulnerable to Code Injection. The `load()` function may execute arbitrary code injected through a malicious YAML file. Objects that have `toString` as key, JavaScript code as value and are used as explicit mapping keys allow attackers to execute the supplied code through the `load()` function. The `safeLoad()` function is unaffected.
An example payload is
`{ toString: !<tag:yaml.org,2002:js/function> 'function (){return Date.now()}' } : 1`
which returns the object
{
"1553107949161": 1
}
## Recommendation
Upgrade to version 3.13.1.
| null |
2021-08-04T20:51:11Z
|
2019-06-04T20:14:07Z
|
HIGH
| 0
|
{'CWE-94'}
|
{'https://www.npmjs.com/advisories/813', 'https://github.com/nodeca/js-yaml/pull/480', 'https://github.com/advisories/GHSA-8j8c-7jfh-h6hx'}
| null |
GHSA
|
GHSA-36vm-xw34-x4pj
|
CHECK-fail in `tf.raw_ops.IRFFT`
|
### Impact
An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.IRFFT`:
```python
import tensorflow as tf
values = [-10.0] * 130
values[0] = -9.999999999999995
inputs = tf.constant(values, shape=[10, 13], dtype=tf.float32)
inputs = tf.cast(inputs, dtype=tf.complex64)
fft_length = tf.constant([0], shape=[1], dtype=tf.int32)
tf.raw_ops.IRFFT(input=inputs, fft_length=fft_length)
```
The above example causes Eigen code to operate on an empty matrix. This triggers on an assertion and causes program termination.
### Patches
We have patched the issue in GitHub commit [1c56f53be0b722ca657cbc7df461ed676c8642a2](https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.
|
{'CVE-2021-29562'}
|
2021-05-21T14:25:02Z
|
2021-05-21T14:25:02Z
|
LOW
| 2.5
|
{'CWE-617'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-29562', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-36vm-xw34-x4pj', 'https://github.com/advisories/GHSA-36vm-xw34-x4pj', 'https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2'}
| null |
GHSA
|
GHSA-g4m3-rpxr-h7vg
|
Malicious Package in mogodb-core
|
This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.
## Recommendation
Remove the package from your environment. There are no indications of further compromise.
| null |
2021-09-30T20:26:34Z
|
2020-09-03T19:52:25Z
|
CRITICAL
| 9.8
|
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1134', 'https://github.com/advisories/GHSA-g4m3-rpxr-h7vg'}
| null |
GHSA
|
GHSA-3j5x-7ccf-ppgm
|
Cross-site scripting in recommender-xblock
|
Recommender before 1.3.1 allows XSS.
|
{'CVE-2018-20858'}
|
2021-08-17T21:16:30Z
|
2019-08-21T16:15:33Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://github.com/advisories/GHSA-3j5x-7ccf-ppgm', 'https://groups.google.com/forum/#!topic/openedx-announce/SF8Sn6MuUTg', 'https://github.com/edx/RecommenderXBlock/pull/2', 'https://nvd.nist.gov/vuln/detail/CVE-2018-20858'}
| null |
GHSA
|
GHSA-4rmr-c2jx-vx27
|
Remote code injection in mustache/mustache
|
In Mustache.php v2.0.0 through v2.14.0, Sections tag can lead to arbitrary php code execution even if strict_callables is true when section value is controllable.
|
{'CVE-2022-0323'}
|
2022-01-28T18:22:22Z
|
2022-01-27T14:51:00Z
|
HIGH
| 8.8
|
{'CWE-1336'}
|
{'https://github.com/advisories/GHSA-4rmr-c2jx-vx27', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0323', 'https://github.com/bobthecow/mustache.php/commit/579ffa5c96e1d292c060b3dd62811ff01ad8c24e', 'https://huntr.dev/bounties/a5f5a988-aa52-4443-839d-299a63f44fb7'}
| null |
GHSA
|
GHSA-jpcm-4485-69p7
|
Sensitive information disclosure via log in com.bmuschko:gradle-vagrant-plugin
|
### Impact
The `com.bmuschko:gradle-vagrant-plugin` Gradle plugin contains an information disclosure vulnerability due to the logging of the system environment variables.
When this Gradle plugin is executed in public CI/CD, this can lead to sensitive credentials being exposed to malicious actors.
### Patches
Fixed in version 3.0.0
### References
- https://github.com/bmuschko/gradle-vagrant-plugin/blob/292129f9343d00d391543fae06239e9b0f33db73/src/main/groovy/com/bmuschko/gradle/vagrant/process/GDKExternalProcessExecutor.groovy#L42-L44
- https://github.com/bmuschko/gradle-vagrant-plugin/issues/19
- https://github.com/bmuschko/gradle-vagrant-plugin/pull/20
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [bmuschko/gradle-vagrant-plugin](https://github.com/bmuschko/gradle-vagrant-plugin)
|
{'CVE-2021-21361'}
|
2022-04-19T19:02:49Z
|
2021-03-09T00:38:41Z
|
HIGH
| 7.4
|
{'CWE-532'}
|
{'https://github.com/advisories/GHSA-jpcm-4485-69p7', 'https://github.com/bmuschko/gradle-vagrant-plugin/blob/292129f9343d00d391543fae06239e9b0f33db73/src/main/groovy/com/bmuschko/gradle/vagrant/process/GDKExternalProcessExecutor.groovy#L42-L44', 'https://github.com/bmuschko/gradle-vagrant-plugin/issues/19', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21361', 'https://github.com/JLLeitschuh/security-research/security/advisories/GHSA-jpcm-4485-69p7', 'https://github.com/bmuschko/gradle-vagrant-plugin/pull/20'}
| null |
GHSA
|
GHSA-rvgg-f8qm-6h7j
|
High severity vulnerability that affects io.vertx:vertx-web
|
In version from 3.0.0 to 3.5.2 of Eclipse Vert.x, the CSRFHandler do not assert that the XSRF Cookie matches the returned XSRF header/form parameter. This allows replay attacks with previously issued tokens which are not expired yet.
|
{'CVE-2018-12540'}
|
2021-01-08T01:57:50Z
|
2018-10-17T16:19:43Z
|
HIGH
| 0
|
{'CWE-352'}
|
{'https://lists.apache.org/thread.html/r10aef585c521f8ef603f5831f9d97a27d920624025131da950e0c62f@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2018:2371', 'https://lists.apache.org/thread.html/rc5b4ae8a7caae6d3d5b3266cb050823b96dd62b30718b90b778d3d8b@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r3fffda8e947edaa359152c8dc4c4ea9c96fd8ced1999bbce92bc6b25@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/r59482ebed302aa49ac7e0c51737499746b0d086fcdeb8f90e705951f@%3Ccommits.pulsar.apache.org%3E', 'https://github.com/advisories/GHSA-rvgg-f8qm-6h7j', 'https://bugs.eclipse.org/bugs/show_bug.cgi?id=536948', 'https://nvd.nist.gov/vuln/detail/CVE-2018-12540'}
| null |
GHSA
|
GHSA-f9fq-vjvh-779p
|
Improper Input Validation in vault-ssh-helper
|
HashiCorp vault-ssh-helper up to and including version 0.1.6 incorrectly accepted Vault-issued SSH OTPs for the subnet in which a host's network interface was located, rather than the specific IP address assigned to that interface. Fixed in 0.2.0.
|
{'CVE-2020-24359'}
|
2022-04-12T22:11:28Z
|
2022-02-15T01:57:18Z
|
HIGH
| 7.5
|
{'CWE-20'}
|
{'https://github.com/advisories/GHSA-f9fq-vjvh-779p', 'https://github.com/hashicorp/vault-ssh-helper/blob/master/CHANGELOG.md#020-august-19-2020', 'https://github.com/hashicorp/vault-ssh-helper/releases', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24359', 'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f'}
| null |
GHSA
|
GHSA-h2fg-54x9-5qhq
|
Nil dereference in NATS JWT, DoS of nats-server
|
## Problem Description
The NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account. The Operator should be able to safely issue Accounts to other entities which it does not fully trust.
A malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution.
The NATS Server is known to be impacted by this.
## Affected versions
#### JWT library
* all versions prior to 1.1.0
#### NATS Server
* Version 2 prior to 2.1.9
## Impact
#### JWT library
* Programs would nil dereference and panic, aborting execution by default.
#### NATS server
* Denial of Service caused by process termination
## Workaround
If your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered.
## Solution
Upgrade the JWT dependency in any application using it.
Upgrade the NATS server if using NATS Accounts.
|
{'CVE-2020-26521'}
|
2022-02-11T23:43:22Z
|
2022-02-11T23:43:13Z
|
LOW
| 7.5
|
{'CWE-476'}
|
{'http://www.openwall.com/lists/oss-security/2020/11/02/2', 'https://advisories.nats.io/CVE/CVE-2020-26521.txt', 'https://github.com/advisories/GHSA-h2fg-54x9-5qhq', 'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/', 'https://github.com/nats-io/nats-server/commits/master', 'https://github.com/nats-io/jwt/security/advisories/GHSA-h2fg-54x9-5qhq', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26521'}
| null |
GHSA
|
GHSA-7r87-cj48-wj45
|
Potential Captcha Validate Bypass in flask-session-captcha
|
### Impact
flask-session-captcha is a package which allows users to extend Flask by adding an image based captcha stored in a server side session.
The `captcha.validate()` function would return `None` if passed no value (e.g. by submitting a request with an empty form).
If implementing users were checking the return value to be **False**, the captcha verification check could be bypassed.
Sample vulnerable code:
```python
if captcha.validate() == False:
... # abort
else:
... # do stuff
```
### Patches
A new version (1.2.1) is available that fixes the issue.
### Workarounds
Users can workaround the issue by not explicitly checking that the value is False.
Checking the return value less explicitly should still work.
```python
if not captcha.validate():
... # abort
else:
... # do stuff
```
```python
if captcha.validate():
... # do stuff
else:
... # abort
```
### References
https://github.com/Tethik/flask-session-captcha/pull/27
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [the github repo](https://github.com/Tethik/flask-session-captcha)
|
{'CVE-2022-24880'}
|
2022-04-27T18:18:03Z
|
2022-04-26T21:19:52Z
|
MODERATE
| 5.3
|
{'CWE-754', 'CWE-394', 'CWE-253'}
|
{'https://github.com/Tethik/flask-session-captcha/commit/2811ae23a38d33b620fb7a07de8837c6d65c13e4', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24880', 'https://github.com/Tethik/flask-session-captcha/releases/tag/v1.2.1', 'https://github.com/advisories/GHSA-7r87-cj48-wj45', 'https://github.com/Tethik/flask-session-captcha/pull/27', 'https://github.com/Tethik/flask-session-captcha/security/advisories/GHSA-7r87-cj48-wj45'}
| null |
GHSA
|
GHSA-8jhx-9gf4-hhf5
|
Improper Access Control in consul
|
The makandra consul gem through 1.0.2 for Ruby has Incorrect Access Control.
|
{'CVE-2019-16377'}
|
2021-08-17T22:33:05Z
|
2019-09-27T20:01:00Z
|
CRITICAL
| 9.8
|
{'CWE-284'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-16377', 'https://github.com/rubysec/ruby-advisory-db/blob/c26fbc13435b8be448ad59131428538049d165e4/gems/consul/CVE-2019-16377.yml', 'https://github.com/makandra/consul/issues/49', 'https://github.com/advisories/GHSA-8jhx-9gf4-hhf5', 'https://rubygems.org/gems/consul'}
| null |
GHSA
|
GHSA-vw47-mr44-3jf9
|
Confused Deputy in Kubernetes
|
A security issue was discovered with Kubernetes that could enable users to send network traffic to locations they would otherwise not have access to via a confused deputy attack.
|
{'CVE-2021-25740'}
|
2021-10-04T14:15:52Z
|
2021-09-21T18:28:30Z
|
LOW
| 3.1
|
{'CWE-610', 'CWE-441'}
|
{'https://github.com/advisories/GHSA-vw47-mr44-3jf9', 'https://github.com/kubernetes/kubernetes/issues/103675', 'https://groups.google.com/g/kubernetes-security-announce/c/WYE9ptrhSLE', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25740'}
| null |
GHSA
|
GHSA-3xv8-3j54-hgrp
|
Out-of-bounds read in Pillow
|
In libImaging/PcxDecode.c in Pillow before 6.2.3 and 7.x before 7.0.1, an out-of-bounds read can occur when reading PCX files where state->shuffle is instructed to read beyond state->buffer.
|
{'CVE-2020-10378'}
|
2021-11-03T18:04:53Z
|
2021-11-03T18:04:53Z
|
MODERATE
| 5.5
|
{'CWE-125'}
|
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/', 'https://github.com/python-pillow/Pillow/commits/master/src/libImaging', 'https://github.com/python-pillow/Pillow/pull/4538', 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10378', 'https://usn.ubuntu.com/4430-2/', 'https://github.com/advisories/GHSA-3xv8-3j54-hgrp', 'https://usn.ubuntu.com/4430-1/', 'https://github.com/python-pillow/Pillow/commit/6a83e4324738bb0452fbe8074a995b1c73f08de7#diff-9478f2787e3ae9668a15123b165c23ac', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/', 'https://github.com/pypa/advisory-db/blob/7872b0a91b4d980f749e6d75a81f8cc1af32829f/vulns/pillow/PYSEC-2020-77.yaml', 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html'}
| null |
GHSA
|
GHSA-94g7-hpv8-h9qm
|
Remote code injection in Log4j
|
### Impact
Logging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input.
More Details:
https://github.com/advisories/GHSA-jfh8-c2jp-5v3q
### Patches
Version 1.11.1 of the Splunk Logging for Java library.
There is also a backport to version 1.6.2 released as a patch: 1.6.2-0-0.
### Workarounds
If upgrading is not possible, then ensure the -Dlog4j2.formatMsgNoLookups=true system property is set on both client- and server-side components.
### References
https://github.com/advisories/GHSA-jfh8-c2jp-5v3q
### For more information
If you have any questions or comments about this advisory:
* Open an issue in https://github.com/splunk/splunk-library-javalogging/issues
* Email us at [devinfo@splunk.com](mailto:devinfo@splunk.com)
| null |
2021-12-14T21:46:35Z
|
2021-12-14T21:46:35Z
|
CRITICAL
| 0
| null |
{'https://github.com/splunk/splunk-library-javalogging/security/advisories/GHSA-94g7-hpv8-h9qm', 'https://github.com/advisories/GHSA-94g7-hpv8-h9qm'}
| null |
GHSA
|
GHSA-qxf4-chvg-4r8r
|
Potential HTTP request smuggling in Apache Tomcat
|
In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
|
{'CVE-2020-1935'}
|
2021-08-19T19:30:38Z
|
2020-02-28T01:10:48Z
|
MODERATE
| 4.8
|
{'CWE-444'}
|
{'https://lists.apache.org/thread.html/r441c1f30a252bf14b07396286f6abd8089ce4240e91323211f1a2d75@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/ra5dee390ad2d60307b8362505c059cd6a726de4d146d63dfce1e05e7@%3Cusers.tomcat.apache.org%3E', 'https://www.debian.org/security/2020/dsa-4680', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://lists.apache.org/thread.html/r80e9c8417c77d52c62809168b96912bda70ddf7748f19f8210f745b1@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/rd547be0c9d821b4b1000a694b8e58ef9f5e2d66db03a31dfe77c4b18@%3Cusers.tomcat.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2020/05/msg00026.html', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/r127f76181aceffea2bd4711b03c595d0f115f63e020348fe925a916c%40%3Cannounce.tomcat.apache.org%3E', 'https://www.debian.org/security/2020/dsa-4673', 'https://lists.apache.org/thread.html/r9ce7918faf347e7aac32be930bf26c233b0b140fe37af0bb294158b6@%3Cdev.tomcat.apache.org%3E', 'http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00025.html', 'https://lists.debian.org/debian-lts-announce/2020/03/msg00006.html', 'https://lists.apache.org/thread.html/r660cd379afe346f10d72c0eaa8459ccc95d83aff181671b7e9076919@%3Cusers.tomcat.apache.org%3E', 'https://lists.apache.org/thread.html/r7bc994c965a34876bd94d5ff15b4e1e30b6220a15eb9b47c81915b78@%3Ccommits.tomee.apache.org%3E', 'https://usn.ubuntu.com/4448-1/', 'https://github.com/advisories/GHSA-qxf4-chvg-4r8r', 'https://lists.apache.org/thread.html/rc31cbabb46cdc58bbdd8519a8f64b6236b2635a3922bbeba0f0e3743@%3Ccommits.tomee.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20200327-0005/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1935', 'https://www.oracle.com/security-alerts/cpuoct2020.html'}
| null |
GHSA
|
GHSA-5q7q-qqw2-hjq7
|
Cross-Site Scripting in AjaxNetProfessional
|
### Overview
Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary JavaScript objects.
### Description
Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it.
XSS effects vary in range from petty nuisance to significant security risk, depending on the sensitivity of the data handled by the vulnerable site and the nature of any security mitigation implemented by the site's owner network.
### Releases
Releases before version 21.12.22.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions.
### Workarounds
A workaround exists that replaces one of the core JavaScript files embedded in the library. Using a XML configuration allows to replace the default JavaScript code to be replaced with the version on GitHub.
```xml
<configuration>
<configSections>
<sectionGroup name="ajaxNet">
<section name="ajaxSettings" type="AjaxPro.AjaxSettingsSectionHandler,AjaxPro.2" requirePermission="false" restartOnExternalChanges="true"/>
</sectionGroup>
</configSections>
<ajaxNet>
<ajaxSettings>
<coreScript>~/ajaxpro-core-fixed.js</coreScript>
</ajaxSettings>
</ajaxNet>
</configuration>
```
Copy the file core.js from the main project folder to your web server root folder and rename that ajaxpro-core-fixed.js.
Clients need to refresh the web page to download the changed JavaScript code.
### References
Commit fixing the issue: c89e39b9679fcb8ab6644fe21cc7e652cb615e2b
Note: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/
### For more information
If you have any questions or comments about this advisory:
* Open an issue on this GitHub repository
|
{'CVE-2021-43853'}
|
2022-04-19T19:03:18Z
|
2022-01-06T18:32:24Z
|
HIGH
| 8.7
|
{'CWE-79'}
|
{'https://github.com/michaelschwarz/Ajax.NET-Professional/security/advisories/GHSA-5q7q-qqw2-hjq7', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43853', 'https://github.com/advisories/GHSA-5q7q-qqw2-hjq7', 'https://github.com/michaelschwarz/Ajax.NET-Professional/releases/tag/v21.12.22.1', 'https://github.com/michaelschwarz/Ajax.NET-Professional/commit/c89e39b9679fcb8ab6644fe21cc7e652cb615e2b'}
| null |
GHSA
|
GHSA-4j59-hfw6-6w7h
|
Downloads Resources over HTTP in cmake
|
Affected versions of `cmake` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `cmake`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available, or installing the cmake binaries via a system package manager, such as `apt-get`.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10642'}
|
2021-09-16T20:54:43Z
|
2018-08-15T19:30:48Z
|
HIGH
| 0
|
{'CWE-311', 'CWE-269'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10642', 'https://nodesecurity.io/advisories/233', 'https://www.npmjs.com/advisories/233', 'https://github.com/advisories/GHSA-4j59-hfw6-6w7h'}
| null |
GHSA
|
GHSA-3vv3-frrq-6486
|
Use of Uninitialized Resource in alg_ds
|
An issue was discovered in the alg_ds crate through 2020-08-25 for Rust. `Matrix::new()` internally calls `Matrix::fill_with()` which uses `*ptr = value` pattern to initialize the buffer. This pattern assumes that there is an initialized struct at the address and drops it, which results in dropping of uninitialized struct.
|
{'CVE-2020-36432'}
|
2021-08-25T20:59:20Z
|
2021-08-25T20:59:20Z
|
CRITICAL
| 9.8
|
{'CWE-665', 'CWE-908'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-36432', 'https://github.com/advisories/GHSA-3vv3-frrq-6486', 'https://gitlab.com/dvshapkin/alg-ds/-/issues/1', 'https://rustsec.org/advisories/RUSTSEC-2020-0033.html'}
| null |
GHSA
|
GHSA-89r3-rcpj-h7w6
|
Path traversal attack on Windows platforms
|
Tapestry processes assets `/assets/ctx` using classes chain `StaticFilesFilter -> AssetDispatcher -> ContextResource`, which doesn't filter the character `\`, so attacker can perform a path traversal attack to read any files on Windows platform.
|
{'CVE-2019-0207'}
|
2021-08-18T22:32:43Z
|
2019-11-18T17:19:03Z
|
HIGH
| 7.5
|
{'CWE-22'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-0207', 'https://lists.apache.org/thread.html/r7d9c54beb1dc97dcccc58d9b5d31f0f7166f9a25ad1beba5f8091e0c@%3Ccommits.tapestry.apache.org%3E', 'https://lists.apache.org/thread.html/bac8d6f9e1b4059b319d9cba6f33219a99b81623476ec896138f851c@%3Cusers.tapestry.apache.org%3E', 'https://lists.apache.org/thread.html/765be3606d865de513f6df9288842c3cf58b09a987c617a535f2b99d@%3Cusers.tapestry.apache.org%3E', 'https://lists.apache.org/thread.html/r87523dd07886223aa086edc25fe9b8ddb9c1090f7db25b068dc30843@%3Ccommits.tapestry.apache.org%3E', 'https://github.com/advisories/GHSA-89r3-rcpj-h7w6'}
| null |
GHSA
|
GHSA-jpv3-g4cc-6vfx
|
Moderate severity vulnerability that affects org.apache.activemq:activemq-client
|
In Apache ActiveMQ 5.0.0 - 5.15.8, unmarshalling corrupt MQTT frame can lead to broker Out of Memory exception making it unresponsive.
|
{'CVE-2019-0222'}
|
2021-07-27T20:32:02Z
|
2019-04-02T15:46:42Z
|
HIGH
| 7.5
|
{'CWE-94'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-0222', 'https://lists.apache.org/thread.html/re4672802b0e5ed67c08c9e77057d52138e062f77cc09581b723cf95a@%3Ccommits.activemq.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00004.html', 'https://lists.apache.org/thread.html/a859563f05fbe7c31916b3178c2697165bd9bbf5a65d1cf62aef27d2@%3Ccommits.activemq.apache.org%3E', 'https://lists.apache.org/thread.html/fcbe6ad00f1de142148c20d813fae3765dc4274955e3e2f3ca19ff7b@%3Cdev.activemq.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/r946488fb942fd35c6a6e0359f52504a558ed438574a8f14d36d7dcd7@%3Ccommits.activemq.apache.org%3E', 'http://activemq.apache.org/security-advisories.data/CVE-2019-0222-announcement.txt', 'http://www.openwall.com/lists/oss-security/2019/03/27/2', 'https://lists.apache.org/thread.html/71640324661c1b6d0b6708bd4fb20170e1b979370a4b8cddc4f8d485@%3Cdev.activemq.apache.org%3E', 'https://lists.apache.org/thread.html/rb698ed085f79e56146ca24ab359c9ef95846618675ea1ef402e04a6d@%3Ccommits.activemq.apache.org%3E', 'https://lists.apache.org/thread.html/7da9636557118178b1690ba0af49c8a7b7b97d925218b5774622f488@%3Cusers.activemq.apache.org%3E', 'https://github.com/advisories/GHSA-jpv3-g4cc-6vfx', 'http://www.securityfocus.com/bid/107622', 'https://lists.apache.org/thread.html/d1e334bd71d6e68462c62c726fe6db565c7a6283302f9c1feed087fa@%3Ccommits.activemq.apache.org%3E', 'https://lists.apache.org/thread.html/03f91b1fb85686a848cee6b90112cf6059bd1b21b23bacaa11a962e1@%3Cdev.activemq.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20190502-0006/', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://lists.apache.org/thread.html/2b5c0039197a4949f29e1e2c9441ab38d242946b966f61c110808bcc@%3Ccommits.activemq.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00005.html'}
| null |
GHSA
|
GHSA-pmpr-55fj-r229
|
Division by zero in TFLite's implementation of `SVDF`
|
### Impact
The implementation of the `SVDF` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/7f283ff806b2031f407db64c4d3edcda8fb9f9f5/tensorflow/lite/kernels/svdf.cc#L99-L102):
```cc
const int rank = params->rank;
...
TF_LITE_ENSURE_EQ(context, num_filters % rank, 0);
```
An attacker can craft a model such that `params->rank` would be 0.
### Patches
We have patched the issue in GitHub commit [6841e522a3e7d48706a02e8819836e809f738682](https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682).
The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
### For more information
Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
### Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
|
{'CVE-2021-29598'}
|
2021-05-21T14:27:58Z
|
2021-05-21T14:27:58Z
|
LOW
| 2.5
|
{'CWE-369'}
|
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pmpr-55fj-r229', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29598', 'https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682', 'https://github.com/advisories/GHSA-pmpr-55fj-r229'}
| null |
GHSA
|
GHSA-4fc7-hc63-7fjg
|
Exposure of repository credentials to external third-party sources in Rancher
|
### Impact
This issue only happens when the user configures access credentials to a private repository in Rancher inside `Apps & Marketplace > Repositories`. It affects Rancher versions 2.5.0 up to and including 2.5.11 and from 2.6.0 up to and including 2.6.2.
An insufficient check of the same-origin policy when downloading Helm charts from a configured private repository can lead to exposure of the repository credentials to a third-party provider. This exposure happens when the private repository:
1. Does an HTTP redirect to a third-party repository or external storage provider.
2. Downloads an icon resource for the chart hosted on a third-party provider.
The address of the private repository is not leaked, only the credentials are leaked in the HTTP `Authorization` header in base64 format.
With the patched versions, the default behavior now is to only send the private repository credentials when subdomain or domain hostname match when following the redirect or downloading external resources.
### Patches
Patched versions include releases 2.5.12, 2.6.3 and later versions.
### Workarounds
1. Update Rancher to a patched version.
2. Check the Helm charts in your configured private repository for possible redirects to third-party storage, and for Helm chart icons from third-party sources.
3. Evaluate any Helm chart that might lead to the mentioned scenario and change affected credentials if deemed necessary.
### References
Information about the same-origin check and how to disable it is available in Rancher [documentation](https://rancher.com/docs/rancher/v2.6/en/helm-charts/#repositories).
### 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/).
|
{'CVE-2021-36778'}
|
2022-05-02T19:33:35Z
|
2022-05-02T19:33:34Z
|
HIGH
| 8.3
|
{'CWE-200'}
|
{'https://github.com/rancher/rancher/security/advisories/GHSA-4fc7-hc63-7fjg', 'https://github.com/advisories/GHSA-4fc7-hc63-7fjg'}
| null |
GHSA
|
GHSA-q4h8-7qff-gh6c
|
Server-side request forgery in Ghost CMS
|
Server-side request forgery (SSRF) vulnerability in Ghost CMS < 3.10.0 allows an attacker to scan local or external network or otherwise interact with internal systems.
|
{'CVE-2020-8134'}
|
2021-05-06T18:28:08Z
|
2021-05-06T18:28:08Z
|
MODERATE
| 8.1
|
{'CWE-918'}
|
{'https://hackerone.com/reports/793704', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8134', 'https://github.com/advisories/GHSA-q4h8-7qff-gh6c'}
| null |
GHSA
|
GHSA-c9c5-9fpr-m882
|
Moderate severity vulnerability that affects sentry-raven
|
The numtok function in lib/raven/okjson.rb in the raven-ruby gem before 0.12.2 for Ruby allows remote attackers to cause a denial of service via a large exponent value in a scientific number.
|
{'CVE-2014-9490'}
|
2021-09-08T21:58:29Z
|
2017-10-24T18:33:36Z
|
MODERATE
| 0
| null |
{'https://exchange.xforce.ibmcloud.com/vulnerabilities/99687', 'https://github.com/getsentry/raven-ruby/commit/477ee93a3f735be33bc1e726820654cdf6e22d8f', 'https://github.com/advisories/GHSA-c9c5-9fpr-m882', 'https://groups.google.com/forum/#!topic/getsentry/Cz5bih0ZY1U', 'https://nvd.nist.gov/vuln/detail/CVE-2014-9490', 'http://seclists.org/oss-sec/2015/q1/26'}
| null |
GHSA
|
GHSA-5q58-x5h2-v5rx
|
Authenticated Privilege Escalation
|
### Impact
Authenticated Privilege Escalation
### Patches
We recommend to update to the current version 6.3.4.1. You can get the update to 6.3.4.1 regularly via the Auto-Updater or directly via the download overview.
https://www.shopware.com/en/download/#shopware-6
### Workarounds
For older versions of 6.1 and 6.2 the corresponding changes are also available via plugin:
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
### For more information
https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-12-2020
| null |
2020-12-21T18:01:08Z
|
2020-12-21T18:01:08Z
|
LOW
| 0
|
{'CWE-863'}
|
{'https://github.com/advisories/GHSA-5q58-x5h2-v5rx', 'https://github.com/shopware/platform/security/advisories/GHSA-5q58-x5h2-v5rx'}
| null |
GHSA
|
GHSA-4rgj-8mq3-hggj
|
Denial of Service in @hapi/subtext
|
Versions of `@hapi/subtext` prior to 6.1.2 are vulnerable to Denial of Service (DoS). The package fails to enforce the `maxBytes` configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.
## Recommendation
Upgrade to version 6.1.2 or later.
| null |
2020-09-03T20:32:11Z
|
2020-09-03T20:32:11Z
|
HIGH
| 0
| null |
{'https://github.com/advisories/GHSA-4rgj-8mq3-hggj', 'https://www.npmjs.com/advisories/1165', 'https://github.com/hapijs/subtext/issues/72'}
| null |
GHSA
|
GHSA-m7rg-8wvq-846v
|
Prototype pollution
|
Prototype pollution vulnerability in 'nestie' versions 0.0.0 through 1.0.0 allows an attacker to cause a denial of service and may lead to remote code execution.
|
{'CVE-2021-25947'}
|
2021-06-14T21:47:45Z
|
2021-06-07T21:49:14Z
|
CRITICAL
| 9.8
|
{'CWE-1321'}
|
{'https://github.com/lukeed/nestie/commit/bc80d5898d1e5e8a3d325d355eda0c325c8dcfc2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25947', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25947', 'https://github.com/advisories/GHSA-m7rg-8wvq-846v'}
| null |
GHSA
|
GHSA-fmr4-w67p-vh8x
|
Moderate severity vulnerability that affects org.wildfly:wildfly-undertow
|
A flaw was found in Wildfly 9.x. A path traversal vulnerability through the org.wildfly.extension.undertow.deployment.ServletResourceManager.getResource method could lead to information disclosure of arbitrary local files.
|
{'CVE-2018-1047'}
|
2021-01-08T20:10:58Z
|
2018-10-19T16:55:35Z
|
MODERATE
| 0
|
{'CWE-20'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2018-1047', 'https://access.redhat.com/errata/RHSA-2018:1248', 'https://bugzilla.redhat.com/show_bug.cgi?id=1528361', 'https://access.redhat.com/errata/RHSA-2018:2938', 'https://github.com/advisories/GHSA-fmr4-w67p-vh8x', 'https://access.redhat.com/errata/RHSA-2018:1249', 'https://access.redhat.com/errata/RHSA-2018:1251', 'https://access.redhat.com/errata/RHSA-2018:1247', 'https://issues.jboss.org/browse/WFLY-9620'}
| null |
GHSA
|
GHSA-657m-v5vm-f6rw
|
Cross-Site-Request-Forgery in Backend
|
> ### Meta
> * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (8.2)
### Problem
It has been discovered that the new TYPO3 v11 feature that allows users to create and share [deep links in the backend user interface](https://typo3.org/article/typo3-version-112-escape-the-orbit#c12178) is vulnerable to cross-site-request-forgery.
The impact is the same as described in [TYPO3-CORE-SA-2020-006 (CVE-2020-11069)](https://typo3.org/security/advisory/typo3-core-sa-2020-006). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system.
To successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time.
The following [Same-Site cookie settings](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.7.x/Feature-90351-ConfigureTYPO3-shippedCookiesWithSameSiteFlag.html) in _$GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite]_ are required for an attack to be successful:
* _SameSite=_***strict***: malicious evil.**example.org** invoking TYPO3 application at good.**example.org**
* _SameSite=_***lax*** or ***none***: malicious **evil.com** invoking TYPO3 application at **example.org**
### Solution
Update your instance to TYPO3 version 11.5.0 which addresses the problem described.
### Credits
Thanks to Richie Lee who reported this issue and to TYPO3 core & security team members Benni Mack and Oliver Hader who fixed the issue.
### References
* [TYPO3-CORE-SA-2021-014](https://typo3.org/security/advisory/typo3-core-sa-2021-014)
* [CVE-2020-11069](https://nvd.nist.gov/vuln/detail/CVE-2020-11069) reintroduced in TYPO3 v11.2.0
|
{'CVE-2021-41113'}
|
2022-04-19T19:03:11Z
|
2021-10-05T20:23:47Z
|
MODERATE
| 8.8
|
{'CWE-352', 'CWE-309'}
|
{'https://github.com/TYPO3/typo3/security/advisories/GHSA-657m-v5vm-f6rw', 'https://typo3.org/security/advisory/typo3-core-sa-2020-006', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11069', 'https://github.com/TYPO3/typo3/commit/fa51999203c5e5d913ecae5ea843ccb2b95fa33f', 'https://github.com/advisories/GHSA-657m-v5vm-f6rw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41113'}
| null |
GHSA
|
GHSA-q76j-58cx-wp5v
|
Vulnerability in RPKI manifest validation
|
A vulnerability in RPKI manifest validation exists when objects on the manifest are hidden, or expired objects are replayed. An attacker successfully exploiting this vulnerability could prevent new ROAs from being received or selectively hide ROAs, causing routes to become INVALID.
To exploit this vulnerability, an attacker would need to perform a man in the middle attack on the TLS connection between the validator and an RRDP repository or perform a man in the middle attack against a rsync-only repository.
The update addresses the vulnerability by implementing validation methods from [RFC 6486bis](https://datatracker.ietf.org/doc/draft-ietf-sidrops-6486bis/00/) and enabling strict validation by default.
| null |
2020-11-13T17:28:49Z
|
2020-11-13T17:28:49Z
|
HIGH
| 0
|
{'CWE-20'}
|
{'https://github.com/RIPE-NCC/rpki-validator-3/security/advisories/GHSA-q76j-58cx-wp5v', 'https://github.com/advisories/GHSA-q76j-58cx-wp5v'}
| null |
GHSA
|
GHSA-6jqj-f58p-mrw3
|
Denial of Service in TenderMint
|
### Description
**Denial of Service**
Tendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network.
Tendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit.
**False Witness**
Tendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **.
_** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._
This can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this.
Tendermint 0.33.6 verifies all the signatures during block execution ***.
_*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._
### Impact
- All nodes
- The network stops due to having a commit with a wrong signature.
### Patches
- v0.33.6
### Workarounds
No workarounds.
### References
- https://github.com/tendermint/tendermint/issues/4926
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)
* Email us at [security@tendermint.com](mailto:security@tendermint.com)
More information can be found [here](https://tendermint.com/security/).
|
{'CVE-2020-15091'}
|
2022-04-19T19:02:29Z
|
2021-12-20T18:17:33Z
|
MODERATE
| 6.5
|
{'CWE-347'}
|
{'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15091', 'https://github.com/tendermint/tendermint/issues/4926', 'https://github.com/advisories/GHSA-6jqj-f58p-mrw3', 'https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3'}
| null |
GHSA
|
GHSA-whc7-5p35-4ww2
|
Use after free in actix-service
|
An issue was discovered in the actix-service crate before 1.0.6 for Rust. The Cell implementation allows obtaining more than one mutable reference to the same data.
|
{'CVE-2020-35899'}
|
2021-08-25T20:49:06Z
|
2021-08-25T20:49:06Z
|
MODERATE
| 5.5
|
{'CWE-416'}
|
{'https://github.com/advisories/GHSA-whc7-5p35-4ww2', 'https://github.com/actix/actix-net/pull/158', 'https://rustsec.org/advisories/RUSTSEC-2020-0046.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35899'}
| null |
GHSA
|
GHSA-fqpx-cq8x-9wp4
|
Unaligned references in sized-chunks
|
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the InlineArray implementation, an unaligned reference may be generated for a type that has a large alignment requirement.
|
{'CVE-2020-25796'}
|
2021-08-25T20:46:03Z
|
2021-08-25T20:46:03Z
|
HIGH
| 7.5
|
{'CWE-129'}
|
{'https://github.com/bodil/sized-chunks/issues/11', 'https://rustsec.org/advisories/RUSTSEC-2020-0041.html', 'https://nvd.nist.gov/vuln/detail/CVE-2020-25796', 'https://github.com/advisories/GHSA-fqpx-cq8x-9wp4'}
| null |
GHSA
|
GHSA-w4rc-rx25-8m86
|
Improper Input Validation in Symfony
|
An issue was discovered in Symfony before 4.2.12 and 4.3.x before 4.3.8. The VarExport component incorrectly escapes strings, allowing some specially crafted ones to escalate to execution of arbitrary PHP code. This is related to symfony/var-exporter.
|
{'CVE-2019-11325'}
|
2021-08-19T17:13:33Z
|
2020-02-12T18:44:16Z
|
CRITICAL
| 9.8
|
{'CWE-116'}
|
{'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-2019-11325.yaml', 'https://symfony.com/blog/cve-2019-11325-fix-escaping-of-strings-in-varexporter', 'https://github.com/symfony/symfony/releases/tag/v4.3.8', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11325', 'https://symfony.com/cve-2019-11325', 'https://github.com/advisories/GHSA-w4rc-rx25-8m86', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/var-exporter/CVE-2019-11325.yaml', 'https://github.com/symfony/var-exporter/compare/d8bf442...57e00f3', 'https://symfony.com/blog/symfony-4-3-8-released'}
| null |
GHSA
|
GHSA-4p3x-8qw9-24w9
|
Authenticated Stored XSS in shopware/shopware
|
### Impact
Authenticated Stored XSS in Administration
### Patches
Use the Security Plugin:
https://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html
### Workarounds
If you cannot use the security plugin, add the following config to your `.htaccess` file
```
<IfModule mod_headers.c>
<FilesMatch "\.(?i:svg)$">
Header set Content-Security-Policy "script-src 'none'"
</FilesMatch>
</IfModule>
```
If you are using nginx as server config, you can add the following to your configuration:
```
server {
# ...
location ~* ^.+\.svg$ {
add_header Content-Security-Policy "script-src 'none'";
}
}
```
### References
https://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021
|
{'CVE-2021-41188'}
|
2021-10-29T13:49:23Z
|
2021-10-27T18:53:18Z
|
MODERATE
| 5.7
|
{'CWE-79'}
|
{'https://github.com/shopware/shopware/releases/tag/v5.7.6', 'https://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41188', 'https://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html', 'https://github.com/advisories/GHSA-4p3x-8qw9-24w9', 'https://github.com/shopware/shopware/commit/37213e91d525c95df262712cba80d1497e395a58', 'https://github.com/shopware/shopware/security/advisories/GHSA-4p3x-8qw9-24w9'}
| null |
GHSA
|
GHSA-7wv8-g97r-432h
|
Exposure of Sensitive Information to an Unauthorized Actor in microweber
|
Exposure of Sensitive Information to an Unauthorized Actor in Packagist microweber/microweber prior to 1.2.11.
|
{'CVE-2022-0281'}
|
2022-01-27T18:32:04Z
|
2022-01-21T18:06:47Z
|
HIGH
| 7.5
|
{'CWE-200'}
|
{'https://github.com/microweber/microweber/commit/e680e134a4215c979bfd2eaf58336be34c8fc6e6', 'https://huntr.dev/bounties/315f5ac6-1b5e-4444-ad8f-802371da3505', 'https://github.com/advisories/GHSA-7wv8-g97r-432h', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0281'}
| null |
GHSA
|
GHSA-wrxc-mr2w-cjpv
|
Open Redirect in Grav
|
Common/Grav.php in Grav before 1.6.23 has an Open Redirect.
|
{'CVE-2020-11529'}
|
2022-01-07T00:20:50Z
|
2022-01-07T00:20:50Z
|
MODERATE
| 6.1
|
{'CWE-601'}
|
{'https://getgrav.org/#changelog', 'https://github.com/advisories/GHSA-wrxc-mr2w-cjpv', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11529', 'https://github.com/getgrav/grav/commit/2eae104c7a4bf32bc26cb8073d5c40464bfda3f7', 'https://github.com/getgrav/grav/issues/3134'}
| null |
GHSA
|
GHSA-6h3m-36w8-hv68
|
Arbitrary file write in nats-server
|
(This document is canonically: <https://advisories.nats.io/CVE/CVE-2022-26652.txt>)
## Background
NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT, and edge computing.
JetStream is the optional RAFT-based resilient persistent feature of NATS.
## Problem Description
The JetStream streams can be backed up and restored via NATS. The backup format is a tar archive file. Inadequate checks on the filenames within the archive file permit a so-called "Zip Slip" attack in the stream restore.
NATS nats-server through 2022-03-09 (fixed in release 2.7.4) did not correctly sanitize elements of the archive file, thus a user of NATS
could cause the NATS server to write arbitrary content to an attacker-controlled filename.
## Affected versions
NATS Server:
* 2.2.0 up to and including 2.7.3.
+ Introduced with JetStream Restore functionality
* Fixed with nats-io/nats-server: 2.7.4
* Docker image: nats <https://hub.docker.com/_/nats>
* NB users of OS package files from our releases: a change in goreleaser defaults, discovered late in the release process, moved the install directory from /usr/local/bin to /usr/bin; we are evaluating the correct solution for subsequent releases, but not recutting this release.
NATS Streaming Server
* 0.15.0 up to and including 0.24.2
* Fixed with nats-io/nats-streaming-server: 0.24.3
* Embeds a nats-server, but this server is the old approach which JetStream replaces, so unlikely (but not impossible) to be
configured with JS support
## Workarounds
* Disable JetStream for untrusted users.
* If only one NATS account uses JetStream, such that cross-user attacks are not an issue, and any user in that account with access to the JetStream API is fully trusted anyway, then appropriate sandboxing techniques will prevent exploit.
+ Eg, with systemd, the supplied util/nats-server-hardened.service example configuration demonstrates that NATS runs fine as an unprivileged user under ProtectSystem=strict and PrivateTmp=true restrictions; by only opening a ReadWritePaths hole for the JetStream storage area, the impact of this vulnerability is limited.
## Solution
Upgrade the NATS server to at least 2.7.4.
We fully support the util/nats-server-hardened.service configuration for running a NATS server and encourage this approach.
## Credits
This issue was reported (on 2022-03-07) to the NATS Maintainers by
Yiming Xiang, TIANJI LAB of NSFOCUS.
Thank you / 谢谢你！
|
{'CVE-2022-26652'}
|
2022-03-24T00:21:11Z
|
2022-03-10T22:07:30Z
|
HIGH
| 6.5
|
{'CWE-22'}
|
{'https://github.com/nats-io/nats-server/releases/tag/v2.7.4', 'https://github.com/nats-io/nats-server/security/advisories/GHSA-6h3m-36w8-hv68', 'https://github.com/nats-io/nats-server/releases', 'http://www.openwall.com/lists/oss-security/2022/03/10/1', 'https://github.com/nats-io/nats-streaming-server/releases/tag/v0.24.3', 'https://advisories.nats.io/CVE/CVE-2022-26652.txt', 'https://github.com/advisories/GHSA-6h3m-36w8-hv68', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26652', 'https://github.com/nats-io/nats-server/pull/2917'}
| null |
GHSA
|
GHSA-3pqg-4rqg-pg9g
|
Cross-site Scripting in OWASP AntiSamy
|
OWASP AntiSamy is a library for performing fast, configurable cleansing of HTML coming from untrusted sources. AntiSamy before 1.6.6 allows XSS via HTML tag smuggling on STYLE content with crafted input. The output serializer does not properly encode the supposed Cascading Style Sheets (CSS) content.
|
{'CVE-2022-28367'}
|
2022-05-04T04:00:41Z
|
2022-04-23T00:03:04Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-28367', 'https://github.com/nahsra/antisamy/commit/0199e7e194dba5e7d7197703f43ebe22401e61ae', 'https://github.com/advisories/GHSA-3pqg-4rqg-pg9g', 'https://github.com/nahsra/antisamy/releases/tag/v1.6.6'}
| null |
GHSA
|
GHSA-hj9h-wrgg-hgmx
|
Data races in lock_api
|
An issue was discovered in the lock_api crate before 0.4.2 for Rust. A data race can occur because of RwLockReadGuard unsoundness.
|
{'CVE-2020-35913'}
|
2021-08-25T20:50:02Z
|
2021-08-25T20:50:02Z
|
MODERATE
| 4.7
|
{'CWE-362'}
|
{'https://github.com/Amanieu/parking_lot/pull/262', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35913', 'https://rustsec.org/advisories/RUSTSEC-2020-0070.html', 'https://github.com/advisories/GHSA-hj9h-wrgg-hgmx'}
| null |
GHSA
|
GHSA-chh2-rvhg-wqwr
|
Malicious Package in json-serializer
|
Version 2.0.10 of `json-serializer` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`
## Recommendation
Remove the package from your environment and evaluate your application to determine whether or not user data was compromised.
| null |
2020-09-03T21:02:10Z
|
2020-09-03T21:02:10Z
|
CRITICAL
| 0
| null |
{'https://www.npmjs.com/advisories/1194', 'https://github.com/advisories/GHSA-chh2-rvhg-wqwr'}
| null |
GHSA
|
GHSA-c6c4-7x48-4cqp
|
Timing side channel vulnerability in UIDL request handler in Vaadin 10, 11-14, and 15-18
|
Non-constant-time comparison of CSRF tokens in UIDL request handler in `com.vaadin:flow-server` versions 1.0.0 through 1.0.13 (Vaadin 10.0.0 through 10.0.16), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.4.6 (Vaadin 14.0.0 through 14.4.6), 3.0.0 prior to 5.0.0 (Vaadin 15 prior to 18), and 5.0.0 through 5.0.2 (Vaadin 18.0.0 through 18.0.5) allows attacker to guess a security token via timing attack.
- https://vaadin.com/security/cve-2021-31404
| null |
2022-04-19T19:02:54Z
|
2021-04-19T14:47:47Z
|
MODERATE
| 4
|
{'CWE-208'}
|
{'https://github.com/advisories/GHSA-c6c4-7x48-4cqp', 'https://vaadin.com/security/cve-2021-31404', 'https://github.com/vaadin/platform/security/advisories/GHSA-c6c4-7x48-4cqp'}
| null |
GHSA
|
GHSA-qf76-pr7x-h7r4
|
Incorrect Access Control in Nacos
|
Nacos 1.1.4 is affected by: Incorrect Access Control. An environment can be set up locally to get the service details interface. Then other Nacos service names can be accessed through the service list interface. Service details can then be accessed when not logged in. (detail:https://github.com/alibaba/nacos/issues/2284)
|
{'CVE-2020-19676'}
|
2021-08-02T16:38:01Z
|
2021-08-02T16:38:01Z
|
MODERATE
| 5.3
|
{'CWE-200'}
|
{'https://github.com/advisories/GHSA-qf76-pr7x-h7r4', 'https://nvd.nist.gov/vuln/detail/CVE-2020-19676', 'https://github.com/alibaba/nacos/issues/2284', 'https://github.com/alibaba/nacos/releases/tag/1.2.0', 'https://github.com/alibaba/nacos/issues/1105'}
| null |
GHSA
|
GHSA-8gvg-8vhf-h26g
|
Out-of-bounds write
|
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0912, CVE-2019-0913, CVE-2019-0914, CVE-2019-0915, CVE-2019-0916, CVE-2019-0917, CVE-2019-0922, CVE-2019-0923, CVE-2019-0924, CVE-2019-0925, CVE-2019-0927, CVE-2019-0933.
|
{'CVE-2019-0937'}
|
2021-03-29T20:59:03Z
|
2021-03-29T20:59:03Z
|
HIGH
| 7.5
|
{'CWE-787'}
|
{'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0937', 'https://github.com/chakra-core/ChakraCore/commit/7827e117753052d479fabe19a25cfece88059bca', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://nvd.nist.gov/vuln/detail/CVE-2019-0937', 'https://github.com/advisories/GHSA-8gvg-8vhf-h26g'}
| null |
GHSA
|
GHSA-93j5-g845-9wqp
|
Unsafe HTTP Redirect in Puppet Agent and Puppet Server
|
A flaw was discovered in Puppet Agent and Puppet Server that may result in a leak of HTTP credentials when following HTTP redirects to a different host. This is similar to CVE-2018-1000007
|
{'CVE-2021-27023'}
|
2021-12-02T17:54:05Z
|
2021-12-02T17:52:45Z
|
MODERATE
| 6.5
| null |
{'https://github.com/advisories/GHSA-93j5-g845-9wqp', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/62SELE7EKVKZL4GABFMVYMIIUZ7FPEF7/', 'https://puppet.com/security/cve/CVE-2021-27023', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27023'}
| null |
GHSA
|
GHSA-7qfm-6m33-rgg9
|
XML External Entity Reference
|
An issue was discovered in service-api before 4.3.12 and 5.x before 5.1.1 for Report Portal. It allows XXE, with resultant secrets disclosure and SSRF, via JUnit XML launch import.
| null |
2021-08-13T15:21:59Z
|
2021-08-13T15:21:59Z
|
HIGH
| 7.5
|
{'CWE-611'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-12642', 'https://github.com/reportportal/reportportal/blob/master/SECURITY_ADVISORIES.md', 'https://github.com/advisories/GHSA-7qfm-6m33-rgg9'}
| null |
GHSA
|
GHSA-8rh6-h94m-vj54
|
Incorrect Comparison in cvxopt
|
Incomplete string comparison vulnerability exits in cvxopt.org cvxop <= 1.2.6 in APIs (cvxopt.cholmod.diag, cvxopt.cholmod.getfactor, cvxopt.cholmod.solve, cvxopt.cholmod.spsolve), which allows attackers to conduct Denial of Service attacks by construct fake Capsule objects.
|
{'CVE-2021-41500'}
|
2022-01-18T22:48:48Z
|
2022-01-07T00:01:11Z
|
HIGH
| 7.5
|
{'CWE-697'}
|
{'https://github.com/cvxopt/cvxopt/issues/193', 'https://github.com/advisories/GHSA-8rh6-h94m-vj54', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41500', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CXTPM3DGVYTYQ54OFCMXZVWVOMR7JM2D/', 'https://github.com/cvxopt/cvxopt/commit/d5a21cf1da62e4269176384b1ff62edac5579f94'}
| null |
GHSA
|
GHSA-x823-j7c4-vpc5
|
Cross-site scripting in sickrage
|
In SiCKRAGE, versions 9.3.54.dev1 to 10.0.11.dev1 are vulnerable to Reflected Cross-Site-Scripting (XSS) due to user input not being validated properly in the `quicksearch` feature. Therefore, an attacker can steal a user's sessionID to masquerade as a victim user, to carry out any actions in the context of the user.
|
{'CVE-2021-25926'}
|
2021-04-23T18:45:59Z
|
2021-04-20T16:31:43Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://github.com/SiCKRAGE/SiCKRAGE/commit/9f42426727e16609ad3d1337f6637588b8ed28e4', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25926,', 'https://github.com/advisories/GHSA-x823-j7c4-vpc5', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25926'}
| null |
GHSA
|
GHSA-j9q7-3rhf-4ppv
|
Downloads Resources over HTTP in windows-selenium-chromedriver
|
Affected versions of `windows-selenium-chromedriver` insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running `windows-selenium-chromedriver`.
## Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
|
{'CVE-2016-10687'}
|
2021-01-14T15:57:22Z
|
2020-09-01T16:11:08Z
|
HIGH
| 0
|
{'CWE-311'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10687', 'https://www.npmjs.com/advisories/285', 'https://github.com/advisories/GHSA-j9q7-3rhf-4ppv', 'https://nodesecurity.io/advisories/285'}
| null |
GHSA
|
GHSA-5x32-c9mf-49cc
|
Directory traversal in RubyGems
|
A Directory Traversal issue was discovered in RubyGems 2.7.6 and later through 3.0.2. Before making new directories or touching files (which now include path-checking code for symlinks), it would delete the target destination. If that destination was hidden behind a symlink, a malicious gem could delete arbitrary files on the user's machine, presuming the attacker could guess at paths. Given how frequently gem is run as sudo, and how predictable paths are on modern systems (/tmp, /usr, etc.), this could likely lead to data loss or an unusable system.
|
{'CVE-2019-8320'}
|
2021-08-17T13:42:36Z
|
2019-06-20T16:06:15Z
|
HIGH
| 7.4
|
{'CWE-22'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-8320', 'https://access.redhat.com/errata/RHSA-2019:1429', 'https://lists.debian.org/debian-lts-announce/2020/08/msg00027.html', 'https://blog.rubygems.org/2019/03/05/security-advisories-2019-03.html', 'https://hackerone.com/reports/317321', 'http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00036.html', 'https://github.com/advisories/GHSA-5x32-c9mf-49cc'}
| null |
GHSA
|
GHSA-m8p2-495h-ccmh
|
The SafeHtml annotation in Hibernate-Validator does not properly guard against XSS attacks
|
A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.
|
{'CVE-2019-10219'}
|
2022-02-11T21:13:08Z
|
2020-01-08T17:01:52Z
|
MODERATE
| 6.5
|
{'CWE-79'}
|
{'https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10219', 'https://security.netapp.com/advisory/ntap-20220210-0024/', 'https://github.com/hibernate/hibernate-validator/commit/20d729548511ac5cff6fd459f93de137195420fe', 'https://access.redhat.com/errata/RHSA-2020:0160', 'https://github.com/hibernate/hibernate-validator/commit/124b7dd6d9a4ad24d4d49f74701f05a13e56ceee', 'https://access.redhat.com/errata/RHSA-2020:0161', 'https://lists.apache.org/thread.html/rb8dca19a4e52b60dab0ab21e2ff9968d78f4b84e4033824db1dd24b4@%3Cpluto-scm.portals.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2020:0159', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10219', 'https://github.com/advisories/GHSA-m8p2-495h-ccmh', 'https://lists.apache.org/thread.html/r4f8b4e2541be4234946e40d55859273a7eec0f4901e8080ce2406fe6@%3Cnotifications.accumulo.apache.org%3E', 'https://lists.apache.org/thread.html/rf9c17c3efc4a376a96e9e2777eee6acf0bec28e2200e4b35da62de4a@%3Cpluto-dev.portals.apache.org%3E', 'https://lists.apache.org/thread.html/r87b7e2d22982b4ca9f88f5f4f22a19b394d2662415b233582ed22ebf@%3Cnotifications.accumulo.apache.org%3E', 'https://lists.apache.org/thread.html/r4f92d7f7682dcff92722fa947f9e6f8ba2227c5dc3e11ba09114897d@%3Cnotifications.accumulo.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2020:0445', 'https://access.redhat.com/errata/RHSA-2020:0164', 'https://lists.apache.org/thread.html/rd418deda6f0ebe658c2015f43a14d03acb8b8c2c093c5bf6b880cd7c@%3Cpluto-dev.portals.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html'}
| null |
GHSA
|
GHSA-8vj2-vxx3-667w
|
Arbitrary expression injection in Pillow
|
PIL.ImageMath.eval in Pillow before 9.0.0 allows evaluation of arbitrary expressions, such as ones that use the Python exec method `ImageMath.eval("exec(exit())")`.
While Pillow 9.0.0 restricted top-level builtins available to PIL.ImageMath.eval(), it did not prevent builtins available to lambda expressions. These are now also restricted in 9.0.1.
|
{'CVE-2022-22817'}
|
2022-04-19T19:03:27Z
|
2022-01-12T20:07:33Z
|
CRITICAL
| 9.8
|
{'CWE-74'}
|
{'https://lists.debian.org/debian-lts-announce/2022/01/msg00018.html', 'https://github.com/python-pillow/Pillow/commit/8531b01d6cdf0b70f256f93092caa2a5d91afc11', 'https://github.com/advisories/GHSA-8vj2-vxx3-667w', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22817', 'https://www.debian.org/security/2022/dsa-5053', 'https://pillow.readthedocs.io/en/stable/releasenotes/9.0.1.html#security', 'https://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#restrict-builtins-available-to-imagemath-eval'}
| null |
GHSA
|
GHSA-9wjh-jr2j-6r4x
|
Remote Code Execution in pi_video_recording
|
All versions of `pi_video_recording` are vulnerable to Remote Code Execution. Due to insufficient input validation the server executes arbitrary code through the /api/record/start endpoint. After running the server, `curl -POST -H "Content-Type: application/json" -d '{"filename": " || touch /tmp/worked;"}' http://localhost:5000/api/record/start`creates a file in the /tmp/ directory
## Recommendation
No fix is currently available. Consider using an alternative module until a fix is made available.
| null |
2021-09-27T15:54:11Z
|
2020-09-02T15:55:58Z
|
HIGH
| 0
|
{'CWE-20'}
|
{'https://github.com/advisories/GHSA-9wjh-jr2j-6r4x', 'https://www.npmjs.com/advisories/773'}
| null |
GHSA
|
GHSA-9xjr-m6f3-v5wm
|
HTTPS MitM vulnerability due to lack of hostname verification
|
An issue was discovered in the hyper crate before 0.9.4 for Rust on Windows. There is an HTTPS man-in-the-middle vulnerability because hostname verification was omitted.
|
{'CVE-2016-10932'}
|
2021-08-25T20:43:06Z
|
2021-08-25T20:43:06Z
|
MODERATE
| 4.8
|
{'CWE-347'}
|
{'https://github.com/hyperium/hyper/blob/master/CHANGELOG.md#v094-2016-05-09', 'https://github.com/advisories/GHSA-9xjr-m6f3-v5wm', 'https://nvd.nist.gov/vuln/detail/CVE-2016-10932', 'https://rustsec.org/advisories/RUSTSEC-2016-0002.html'}
| null |
GHSA
|
GHSA-5h46-h7hh-c6x9
|
Integer Overflow in Chunked Transfer-Encoding
|
### Summary
hyper's HTTP server and client code had a flaw that could trigger an integer overflow when decoding chunk sizes that are too big. This allows possible data loss, or if combined with an upstream HTTP proxy that allows chunk sizes larger than hyper does, can result in "request smuggling" or "desync attacks".
### Vulnerability
Example:
```
GET / HTTP/1.1
Host: example.com
Transfer-Encoding: chunked
f0000000000000003
abc
0
```
hyper only reads the rightmost 64-bit integer as the chunk size. So it reads `f0000000000000003` as `3`. A loss of data can occur since hyper would then read only 3 bytes of the body. Additionally, an HTTP request smuggling vulnerability would occur if using a proxy which instead has prefix truncation in the chunk size, or that understands larger than 64-bit chunk sizes.
Read more about desync attacks: https://portswigger.net/research/http-desync-attacks-request-smuggling-reborn
### Impact
To determine if vulnerable to _data loss_, these things must be true:
- **Using HTTP/1.1.** Since HTTP/2 does not use chunked encoding, it is not vulnerable.
- **Using hyper as a server or client.** The body would be improperly truncated in either case.
- **Users send requests or responses with chunk sizes greater than 18 exabytes**.
To determine if vulnerable to _desync attacks_, these things must be true:
- **Using an upstream proxy that allows chunks sizes larger than 64-bit.** If the proxy rejects chunk sizes that are too large, that request won't be forwarded to hyper.
### Patches
We have released the following patch versions:
- v0.14.10 (to be released when this advisory is published)
### Workarounds
Besides upgrading hyper, you can take the following options:
- Reject requests manually that contain a `Transfer-Encoding` header.
- Ensure any upstream proxy rejects `Transfer-Encoding` chunk sizes greater than what fits in 64-bit unsigned integers.
### Credits
This issue was initially reported by [Mattias Grenfeldt](https://grenfeldt.dev/) and Asta Olofsson.
|
{'CVE-2021-32714'}
|
2022-04-19T19:03:01Z
|
2021-07-12T16:55:37Z
|
MODERATE
| 5.9
|
{'CWE-190'}
|
{'https://rustsec.org/advisories/RUSTSEC-2021-0079.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32714', 'https://github.com/advisories/GHSA-5h46-h7hh-c6x9', 'https://github.com/hyperium/hyper/security/advisories/GHSA-5h46-h7hh-c6x9'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.