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-5rq8-3wvf-wrfg
|
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-0937.
|
{'CVE-2019-0933'}
|
2021-03-29T20:59:01Z
|
2021-03-29T20:59:01Z
|
HIGH
| 7.5
|
{'CWE-787'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-0933', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/advisories/GHSA-5rq8-3wvf-wrfg', 'https://github.com/chakra-core/ChakraCore/commit/1a550c67b33b27675c0553152cabd09e4ffe3abf', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0933'}
| null |
GHSA
|
GHSA-4365-fhm5-qcrx
|
Maliciously Crafted Model Archive Can Lead To Arbitrary File Write
|
### Impact
An Archive Extraction (Zip Slip) vulnerability in the functionality that allows a user to load a trained model archive in Rasa 2.8.9 and older allows an attacker arbitrary write capability within specific directories using a malicious crafted archive file.
### Patches
The vulnerability is fixed in Rasa 2.8.10
### Workarounds
Mitigating steps for vulnerable end users are to ensure that they do not upload untrusted model files, and restrict CLI or API endpoint access where a malicious actor could target a deployed Rasa instance.
### For more information
If you have any questions or comments about this advisory:
* Email [the Rasa Security Team](mailto:security@rasa.com)
|
{'CVE-2021-41127'}
|
2021-10-22T16:19:13Z
|
2021-10-22T16:19:13Z
|
HIGH
| 7.3
|
{'CWE-23', 'CWE-22'}
|
{'https://github.com/advisories/GHSA-4365-fhm5-qcrx', 'https://github.com/RasaHQ/rasa/commit/1b6b502f52d73b4f8cd1959ce724b8ad0eb33989', 'https://github.com/RasaHQ/rasa/security/advisories/GHSA-4365-fhm5-qcrx'}
| null |
GHSA
|
GHSA-wh77-3x4m-4q9g
|
Moderate severity vulnerability that affects bootstrap and bootstrap-sass
|
In Bootstrap 4 before 4.3.1 and Bootstrap 3 before 3.4.1, XSS is possible in the tooltip or popover data-template attribute. For more information, see: https://blog.getbootstrap.com/2019/02/13/bootstrap-4-3-1-and-3-4-1/
|
{'CVE-2019-8331'}
|
2021-12-03T14:54:43Z
|
2019-02-22T20:54:27Z
|
MODERATE
| 0
| null |
{'https://github.com/advisories/GHSA-wh77-3x4m-4q9g'}
| null |
GHSA
|
GHSA-r23g-3qw4-gfh2
|
Moderate severity vulnerability that affects redcloth
|
Cross-site scripting (XSS) vulnerability in the RedCloth library 4.2.9 for Ruby and earlier allows remote attackers to inject arbitrary web script or HTML via a javascript: URI.
|
{'CVE-2012-6684'}
|
2022-04-19T19:03:25Z
|
2017-10-24T18:33:37Z
|
MODERATE
| 0
|
{'CWE-79'}
|
{'https://gist.github.com/co3k/75b3cb416c342aa1414c', 'http://jgarber.lighthouseapp.com/projects/13054-redcloth/tickets/243-xss', 'http://co3k.org/blog/redcloth-unfixed-xss-en', 'https://github.com/advisories/GHSA-r23g-3qw4-gfh2', 'https://nvd.nist.gov/vuln/detail/CVE-2012-6684', 'http://seclists.org/fulldisclosure/2014/Dec/50', 'http://www.debian.org/security/2015/dsa-3168'}
| null |
GHSA
|
GHSA-624f-cqvr-3qw4
|
URL Redirection to Untrusted Site ('Open Redirect') in Flask-AppBuilder
|
### Impact
If using Flask-AppBuilder OAuth, an attacker can share a carefully crafted URL with a trusted domain for an application built with Flask-AppBuilder, this URL can redirect a user to a malicious site. This is an open redirect vulnerability
### Patches
Install Flask-AppBuilder 3.2.2 or above
### Workarounds
Filter HTTP traffic containing `?next={next-site}` where the `next-site` domain is different from the application you are protecting
|
{'CVE-2021-32805'}
|
2021-09-09T13:33:27Z
|
2021-09-08T21:11:14Z
|
HIGH
| 7.2
|
{'CWE-601'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-32805', 'https://github.com/dpgaspar/Flask-AppBuilder/commit/6af28521589599b1dbafd6313256229ee9a4fa74', 'https://github.com/advisories/GHSA-624f-cqvr-3qw4', 'https://pypi.org/project/Flask-AppBuilder/', 'https://github.com/dpgaspar/Flask-AppBuilder/releases/tag/v3.3.2', 'https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-624f-cqvr-3qw4'}
| null |
GHSA
|
GHSA-cpp2-q66x-fq44
|
Directory Traversal in jikes
|
Affected versions of `jikes` resolve relative file paths, resulting in a directory traversal vulnerability. A malicious actor can use this vulnerability to access files outside of the intended directory root, which may result in the disclosure of private files on the vulnerable system.
Example request:
```
GET /../../../../../../../../../../etc/passwd HTTP/1.1
host:foo
```
## Recommendation
No patch is available for this vulnerability.
It is recommended that the package is only used for local development, and if the functionality is needed for production, a different package is used instead.
|
{'CVE-2017-16139'}
|
2021-01-08T18:57:23Z
|
2018-08-06T21:39:12Z
|
MODERATE
| 0
|
{'CWE-22'}
|
{'https://github.com/advisories/GHSA-cpp2-q66x-fq44', 'https://github.com/JacksonGL/NPM-Vuln-PoC/blob/master/directory-traversal/jikes', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16139', 'https://nodesecurity.io/advisories/476', 'https://www.npmjs.com/advisories/476'}
| null |
GHSA
|
GHSA-w23f-f3c5-r9qh
|
Downloads Resources over HTTP in ikst
|
Affected versions of `ikst` insecurely download resources over HTTP.
In scenarios where an attacker has a privileged network position, they can modify or read such resources at will. While the exact severity of impact for a vulnerability like this is highly variable and depends on the behavior of the package itself, it ranges from being able to read sensitive information all the way up to and including remote code execution.
## Recommendation
Upgrade to version 1.1.2 or greater.
|
{'CVE-2017-16041'}
|
2021-01-08T01:57:11Z
|
2018-07-24T15:56:19Z
|
HIGH
| 0
|
{'CWE-311'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2017-16041', 'https://www.npmjs.com/advisories/249', 'https://nodesecurity.io/advisories/249', 'https://github.com/advisories/GHSA-w23f-f3c5-r9qh'}
| null |
GHSA
|
GHSA-58mj-pw57-4vm2
|
Cross-site scripting in PHPMailer
|
PHPMailer versions prior to 5.2.24 (released July 26th 2017) have an XSS vulnerability in one of the code examples, CVE-2017-11503. The code_generator.phps example did not filter user input prior to output. This file is distributed with a `.phps` extension, so it it not normally executable unless it is explicitly renamed, and the file is not included when PHPMailer is loaded through composer, so it is safe by default. There was also an undisclosed potential XSS vulnerability in the default exception handler (unused by default). Patches for both issues kindly provided by Patrick Monnerat of the Fedora Project.
### Impact
PHPMailer 5.2.23 has XSS in the "From Email Address" and "To Email Address" fields of code_generator.php.
### Patches
Fixed in 5.2.24
### Workarounds
None.
### References
https://nvd.nist.gov/vuln/detail/CVE-2017-11503
### For more information
If you have any questions or comments about this advisory:
* Open a private issue in [the PHPMailer project](https://github.com/PHPMailer/PHPMailer)
|
{'CVE-2017-11503'}
|
2021-08-19T19:44:10Z
|
2020-03-05T22:09:13Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://cxsecurity.com/issue/WLB-2017060181', 'https://github.com/advisories/GHSA-58mj-pw57-4vm2', 'https://github.com/PHPMailer/PHPMailer/security/advisories/GHSA-58mj-pw57-4vm2', 'https://github.com/PHPMailer/PHPMailer/releases/tag/v5.2.24', 'https://nvd.nist.gov/vuln/detail/CVE-2017-11503', 'http://www.securityfocus.com/bid/99293/', 'https://packetstormsecurity.com/files/143138/phpmailer-xss.txt', 'https://github.com/FriendsOfPHP/security-advisories/blob/master/phpmailer/phpmailer/CVE-2017-11503.yaml', 'http://www.securitytracker.com/id/1039026'}
| null |
GHSA
|
GHSA-694p-xrhg-x3wm
|
CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request Header Injection')
|
### Vulnerability
Micronaut's HTTP client is vulnerable to "HTTP Request Header Injection" due to not validating request headers passed to the client.
Example of vulnerable code:
```java
@Controller("/hello")
public class HelloController {
@Inject
@Client("/")
RxHttpClient client;
@Get("/external-exploit")
@Produces(MediaType.TEXT_PLAIN)
public String externalExploit(@QueryValue("header-value") String headerValue) {
return client.toBlocking().retrieve(
HttpRequest.GET("/hello")
.header("Test", headerValue)
);
}
}
```
In the above case a query value received from a user is passed as a header value to the client. Since the client doesn't validate the header value the request headers and body have the potential to be manipulated.
For example, a user that supplies the following payload, can force the client to make multiple attacker-controlled HTTP requests.
```java
List<String> headerData = List.of(
"Connection: Keep-Alive", // This keeps the connection open so another request can be stuffed in.
"",
"",
"POST /hello/super-secret HTTP/1.1",
"Host: 127.0.0.1",
"Content-Length: 31",
"",
"{\"new\":\"json\",\"content\":\"here\"}",
"",
""
);
String headerValue = "H\r\n" + String.join("\r\n", headerData);;
URI theURI =
UriBuilder
.of("/hello/external-exploit")
.queryParam("header-value", headerValue) // Automatically URL encodes data
.build();
HttpRequest<String> request = HttpRequest.GET(theURI);
String body = client.toBlocking().retrieve(request);
```
Note that using `@HeaderValue` instead of `@QueryValue` is not vulnerable since Micronaut's HTTP server does validate the headers passed to the server, so the exploit can only be triggered by using user data that is not an HTTP header (query values, form data etc.).
### Impact
The attacker is able to control the entirety of the HTTP body for their custom requests.
As such, this vulnerability enables attackers to perform a variant of [Server Side Request Forgery](https://cwe.mitre.org/data/definitions/918.html).
### Patches
The problem has been patched in the `micronaut-http-client` versions 1.2.11 and 1.3.2 and above.
### Workarounds
Do not pass user data directly received from HTTP request parameters as headers in the HTTP client.
### References
Fix commits
- https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1
- https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d
- https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [micronaut-core](https://github.com/micronaut-projects/micronaut-core)
* Email us at [info@micronaut.io](mailto:info@micronaut.io)
### Credit
Originally reported by @JLLeitschuh
|
{'CVE-2020-7611'}
|
2022-04-19T19:02:23Z
|
2020-03-30T20:54:55Z
|
CRITICAL
| 9.8
|
{'CWE-444'}
|
{'https://github.com/micronaut-projects/micronaut-core/security/advisories/GHSA-694p-xrhg-x3wm', 'https://github.com/micronaut-projects/micronaut-core/commit/bc855e439c4a5ced3d83195bb59d0679cbd95add', 'https://snyk.io/vuln/SNYK-JAVA-IOMICRONAUT-561342', 'https://github.com/micronaut-projects/micronaut-core/commit/6deb60b75517f80c57b42d935f07955c773b766d', 'https://github.com/micronaut-projects/micronaut-core/commit/9d1eff5c8df1d6cda1fe00ef046729b2a6abe7f1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7611', 'https://github.com/advisories/GHSA-694p-xrhg-x3wm'}
| null |
GHSA
|
GHSA-4w23-c97g-fq5v
|
snipe-it is vulnerable to Cross-Site Request Forgery (CSRF)
|
snipe-it is vulnerable to Cross-Site Request Forgery (CSRF)
|
{'CVE-2021-4130'}
|
2022-01-05T20:33:16Z
|
2022-01-05T20:33:16Z
|
HIGH
| 8.8
|
{'CWE-352'}
|
{'https://huntr.dev/bounties/ccf073cd-7f54-4d51-89f2-6b4a2e4ae81e', 'https://github.com/advisories/GHSA-4w23-c97g-fq5v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-4130', 'https://github.com/snipe/snipe-it/commit/9b2dd6522f214a3fbee6a4e32699104d0ea2b6ae'}
| null |
GHSA
|
GHSA-h6h5-6fmq-rh28
|
Path traversal allows leaking out-of-bound files from Argo CD repo-server
|
### Impact
All unpatched versions of Argo CD starting with v1.5.0 are vulnerable to a path traversal vulnerability allowing a malicious user with read/write access to leak sensitive files from Argo CD's repo-server.
A malicious Argo CD user who has been granted [`create` or `update` access to Applications](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions) can leak the contents of any text file on the repo-server. By crafting a malicious Helm chart and using it in an Application, the attacker can retrieve the sensitive file's contents either as part of the generated manifests or in an error message. The attacker would have to know or guess the location of the target file.
Sensitive files which could be leaked include files from other Application's source repositories (potentially decrypted files, if you are using a decryption plugin) or any secrets which have been mounted as files on the repo-server.
### Patches
A patch for this vulnerability has been released in the following Argo CD versions:
* v2.3.0
* v2.2.6
* v2.1.11
### Workarounds
The only certain way to avoid the vulnerability is to upgrade.
To mitigate the problem, you can
* avoid storing secrets in git
* avoid mounting secrets as files on the repo-server
* avoid decrypting secrets into files on the repo-server
* carefully [limit who can `create` or `update` Applications](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#rbac-resources-and-actions)
### References
* [Security documentation for the repo-server component](https://argo-cd.readthedocs.io/en/stable/operator-manual/security/#git-helm-repositories)
* [Argo CD RBAC configuration documentation](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/#)
### For more information
Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions)
Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd
|
{'CVE-2022-24731'}
|
2022-03-29T21:52:11Z
|
2022-03-24T00:12:46Z
|
MODERATE
| 6.8
|
{'CWE-284', 'CWE-22'}
|
{'https://github.com/argoproj/argo-cd/security/advisories/GHSA-h6h5-6fmq-rh28', 'https://github.com/advisories/GHSA-h6h5-6fmq-rh28', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24731'}
| null |
GHSA
|
GHSA-m8gw-hjpr-rjv7
|
Prototype Pollution in dojo
|
All versions of package dojo are vulnerable to Prototype Pollution via the setObject function.
|
{'CVE-2021-23450'}
|
2022-04-22T15:39:59Z
|
2022-01-05T15:01:46Z
|
HIGH
| 7.5
|
{'CWE-1321'}
|
{'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWER-2313035', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23450', 'https://snyk.io/vuln/SNYK-JS-DOJO-1535223', 'https://github.com/advisories/GHSA-m8gw-hjpr-rjv7', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARS-2313036', 'https://github.com/dojo/dojo/blob/4c39c14349408fc8274e19b399ffc660512ed07c/_base/lang.js%23L172', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-2313033', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSBOWERGITHUBDOJO-2313034'}
| null |
GHSA
|
GHSA-pv4c-p2j5-38j4
|
Open Redirect in url-parse
|
Versions of `url-parse` before 1.4.3 returns the wrong hostname which could lead to Open Redirect, Server Side Request Forgery (SSRF), or Bypass Authentication Protocol vulnerabilities.
## Recommendation
Update to version 1.4.3 or later.
|
{'CVE-2018-3774'}
|
2021-01-08T18:18:31Z
|
2018-08-13T15:02:15Z
|
HIGH
| 0
|
{'CWE-425'}
|
{'https://github.com/advisories/GHSA-pv4c-p2j5-38j4', 'https://hackerone.com/reports/384029', 'https://nvd.nist.gov/vuln/detail/CVE-2018-3774', 'https://www.npmjs.com/advisories/678', 'https://github.com/unshiftio/url-parse/commit/53b1794e54d0711ceb52505e0f74145270570d5a', 'https://github.com/unshiftio/url-parse/commit/d7b582ec1243e8024e60ac0b62d2569c939ef5de'}
| null |
GHSA
|
GHSA-phwq-j96m-2c2q
|
Template injection in ejs
|
The ejs (aka Embedded JavaScript templates) package 3.1.6 for Node.js allows server-side template injection in settings[view options][outputFunctionName]. This is parsed as an internal option, and overwrites the outputFunctionName option with an arbitrary OS command (which is executed upon template compilation).
|
{'CVE-2022-29078'}
|
2022-04-27T14:36:25Z
|
2022-04-26T00:00:40Z
|
HIGH
| 0
|
{'CWE-74'}
|
{'https://github.com/mde/ejs/commit/15ee698583c98dadc456639d6245580d17a24baf', 'https://eslam.io/posts/ejs-server-side-template-injection-rce/', 'https://nvd.nist.gov/vuln/detail/CVE-2022-29078', 'https://github.com/advisories/GHSA-phwq-j96m-2c2q'}
| null |
GHSA
|
GHSA-xw79-hhv6-578c
|
Cross-Site Scripting in serve
|
Versions of `serve` prior to 10.0.2 are vulnerable to Cross-Site Scripting (XSS). The package does not encode output, allowing attackers to execute arbitrary JavaScript in the victim's browser if user-supplied input is rendered.
## Recommendation
Upgrade to version 10.0.2 or later.
| null |
2021-09-28T16:54:34Z
|
2020-09-11T21:16:59Z
|
HIGH
| 0
|
{'CWE-79'}
|
{'https://hackerone.com/reports/398285', 'https://github.com/advisories/GHSA-xw79-hhv6-578c', 'https://www.npmjs.com/advisories/971', 'https://hackerone.com/reports/358641', 'https://github.com/zeit/serve-handler/commit/65b4d4183a31a8076c78c40118acb0ca1b64f620'}
| null |
GHSA
|
GHSA-4m3j-h8f2-4xh4
|
Malicious Package in coinstrig
|
All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.
## 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-10-01T20:58:37Z
|
2020-09-03T19:41:31Z
|
CRITICAL
| 9.1
|
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1384', 'https://github.com/advisories/GHSA-4m3j-h8f2-4xh4'}
| null |
GHSA
|
GHSA-3qpr-7rmg-73v8
|
Moderate severity vulnerability that affects Plone and Zope2
|
AccessControl/AuthEncoding.py in Zope before 2.13.19, as used in Plone before 4.2.3 and 4.3 before beta 1, allows remote attackers to obtain passwords via vectors involving timing discrepancies in password validation.
|
{'CVE-2012-5507'}
|
2021-06-11T14:39:25Z
|
2018-07-23T19:51:02Z
|
MODERATE
| 0
|
{'CWE-362'}
|
{'https://github.com/advisories/GHSA-3qpr-7rmg-73v8', 'http://www.openwall.com/lists/oss-security/2012/11/10/1', 'https://nvd.nist.gov/vuln/detail/CVE-2012-5507', 'https://bugs.launchpad.net/zope2/+bug/1071067', 'https://plone.org/products/plone/security/advisories/20121106/23', 'https://plone.org/products/plone-hotfix/releases/20121106', 'https://github.com/plone/Products.CMFPlone/blob/4.2.3/docs/CHANGES.txt'}
| null |
GHSA
|
GHSA-qm7x-rc44-rrqw
|
Cross-site Scripting Vulnerability in GraphQL Playground (distributed by Apollo Server)
|
### Impact
In certain configurations, Apollo Server serves the client-side web app "GraphQL Playground" from the same web server that executes GraphQL operations. This web app has access to cookies and other credentials associated with the web server's operations. There is a cross-site scripting vulnerability in GraphQL Playground that allows for arbitrary JavaScript code execution in your web server's origin. If a user clicks a specially crafted link to your GraphQL Playground page served by Apollo Server, an attacker can steal cookies and other private browser data.
Details of the underlying GraphQL Playground vulnerability are available in [this `graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7). (A [similar vulnerability](https://github.com/graphql/graphiql/security/advisories/GHSA-x4r7-m2q9-69c8) exists in the related `graphiql` project.) This advisory focuses on identifying whether *Apollo Server* installations are vulnerable and mitigating the vulnerability in Apollo Server; see the other advisories for details on the XSS vulnerability itself.
The impact of this vulnerability is more severe if (as is common) your GraphQL server's origin URL is an origin that is used to store sensitive data such as cookies.
In order for this vulnerability to affect your Apollo Server installation, it must actually serve GraphQL Playground. The integration between Apollo Server and GraphQL Playground is different in Apollo Server 2 and Apollo Server 3. You can tell which version of Apollo Server you are running by looking at the version of the [package from which you import the `ApolloServer` class](https://www.apollographql.com/docs/apollo-server/integrations/middleware/): this may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc.
#### Apollo Server 3
Apollo Server 3 does not serve GraphQL Playground by default. It has a [landing page plugin system](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) and the default plugin is a simple splash page that is not vulnerable to this exploit, linking to Apollo Sandbox Explorer. (We chose to change the default because GraphQL Playground is not actively maintained.)
If you are running Apollo Server 3, then you are *only* vulnerable if you *explicitly* import the [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) plugin and pass it to your `ApolloServer`'s constructor in the `plugins` array. Otherwise, this advisory does not apply to your server.
#### Apollo Server 2
Apollo Server 2 serves GraphQL Playground by default, unless the `NODE_ENV` environment variable is set to `production`, or if you explicitly configure it via the `playground` option to the `ApolloServer` constructor.
Your Apollo Server 2 installation is vulnerable if *any* of the following is true:
- You pass `playground: true` to the `ApolloServer` constructor
- You pass some other object like `playground: {title: "Title"}` to the `ApolloServer` constructor
- You do *not* pass any `playground` option to the `ApolloServer` constructor, *and* the `NODE_ENV` environment variable is *not* set to `production`
#### Apollo Server 1
Apollo Server 1 included `graphiql` instead of `graphql-playground`. `graphiql` isn't automatically enabled in Apollo Server 1: you have to explicitly call a function such as `graphiqlExpress` to enable it. Because Apollo Server 1 is not commonly used, we have not done a detailed examination of whether the integration between Apollo Server 1 and `graphiql` is vulnerable to a similar exploit. If you are still using Apollo Server 1, we recommend you disable `graphiql` by removing the `graphiqlExpress` call, and then upgrade to a newer version of Apollo Server.
### Patches and workarounds
There are several approaches you can take to ensure that your server is not vulnerable to this issue.
#### Upgrade Apollo Server
The vulnerability has been patched in Apollo Server 2.25.3 and Apollo Server 3.4.1. To get the patch, upgrade your [Apollo Server entry point package](https://www.apollographql.com/docs/apollo-server/integrations/middleware/) to one of the fixed versions; this package may be `apollo-server`, `apollo-server-express`, `apollo-server-lambda`, etc. Additionally, if you depend directly on `apollo-server-core` in your `package.json`, make sure that you upgrade it to the same version.
#### Upgrade Playground version only
If upgrading to the latest version of Apollo Server 2 or 3 quickly will be challenging, you can configure your current version of Apollo Server to serve the latest version of the GraphQL Playground app. This will pin your app to serve a specific version of GraphQL Playground and you will not receive updates to it when you upgrade Apollo Server later, but this may be acceptable because GraphQL Playground is not actively maintained.
The way to do this depends on what version of Apollo Server you're using and if you're already configuring GraphQL Playground.
- **Apollo Server 3**: If you are using Apollo Server 3, then you are only vulnerable if your serve explicitly calls [`ApolloServerPluginLandingPageGraphQLPlayground`](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/#graphql-playground-landing-page) and passes it to the Apollo Server constructor in the `plugins` array. Add the option `version: '1.7.42'` to this call, so it looks like:
```
plugins: [ApolloServerPluginLandingPageGraphQLPlayground({version: '1.7.42'})]
```
- **Apollo Server 2 with no explicit `playground` option**: If you are using Apollo Server 2 and do not currently pass the `playground` option to `new ApolloServer`, add a `playground` option like so:
```
new ApolloServer({ playground: process.env.NODE_ENV === 'production' ? false : { version: '1.7.42' } })
```
- **Apollo Server 2 with `playground: true` or `playground: {x, y, z}`**: If you are using Apollo Server 2 and currently pass `true` or an object to `new ApolloServer`, pass the `version` option under the `playground` option like so:
```
new ApolloServer({ playground: { version: '1.7.42', x, y, z } })
```
#### Disable GraphQL Playground
If upgrading Apollo Server or GraphQL Playground is challenging, you can also disable GraphQL Playground.
In Apollo Server 3, remove the call to `ApolloServerPluginLandingPageGraphQLPlayground` from your `ApolloServer` constructor's `plugins` array. This will replace GraphQL Playground with a simple splash page. See [the landing page plugins docs](https://www.apollographql.com/docs/apollo-server/api/plugin/landing-pages/) for details.
In Apollo Server 2, add `playground: false` to your `ApolloServer` constructor: `new ApolloServer({ playground: false })`. This will replace GraphQL Playground with an attempt to execute a GraphQL operation, which will likely display an error in the browser.
If you disable GraphQL Playground, any users who rely on it to execute GraphQL operations will need an alternative, such as the [Apollo Studio Explorer's account-free Sandbox](https://www.apollographql.com/docs/studio/explorer/#account-free-sandbox).
### Credit
This vulnerability was discovered by @Ry0taK. Thank you!
The fix to GraphQL Playground was developed by @acao and @glasser with help from @imolorhe, @divyenduz, and @benjie.
### For more information
If you have any questions or comments about this advisory:
* Read the [`graphql-playground` advisory](https://github.com/graphql/graphql-playground/security/advisories/GHSA-59r9-6jp6-jcm7)
* Open an issue in [the `apollo-server` repo](https://github.com/apollographql/apollo-server/)
* If the issue involves confidential information, email us at [security@apollographql.com](mailto:security@apollographql.com)
| null |
2022-04-19T19:03:07Z
|
2021-11-08T18:07:42Z
|
HIGH
| 0
|
{'CWE-79'}
|
{'https://github.com/advisories/GHSA-qm7x-rc44-rrqw', 'https://github.com/apollographql/apollo-server/security/advisories/GHSA-qm7x-rc44-rrqw'}
| null |
GHSA
|
GHSA-xrpj-f9v6-2332
|
CSV injection in Craft CMS
|
# Withdrawn
Duplicate of GHSA-h7vq-5qgw-jwwq
| null |
2021-10-18T19:09:51Z
|
2021-10-04T20:12:45Z
|
HIGH
| 8.8
|
{'CWE-1236', 'CWE-74'}
|
{'https://github.com/craftcms/cms/security/advisories/GHSA-h7vq-5qgw-jwwq', 'https://github.com/advisories/GHSA-xrpj-f9v6-2332', 'https://twitter.com/craftcmsupdates/status/1442928690145366018', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41824', 'https://github.com/craftcms/cms/blob/develop/CHANGELOG.md#3714---2021-09-28', 'https://github.com/craftcms/cms/commit/c9cb2225f1b908fb1e8401d401219228634b26b2'}
| null |
GHSA
|
GHSA-2r2w-jrh2-p4gr
|
Cross-site Scripting in LibreNMS
|
In LibreNMS < 21.3.0, a stored XSS vulnerability was identified in the API Access page due to insufficient sanitization of the $api->description variable. As a result, arbitrary Javascript code can get executed.
|
{'CVE-2021-31274'}
|
2021-09-09T17:08:55Z
|
2021-09-09T17:08:55Z
|
MODERATE
| 0
|
{'CWE-79'}
|
{'https://github.com/advisories/GHSA-2r2w-jrh2-p4gr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31274', 'https://github.com/librenms/librenms/pull/12739', 'https://community.librenms.org/t/vulnerability-report-cross-site-scripting-xss-in-the-api-access-page/15431', 'https://github.com/librenms/librenms'}
| null |
GHSA
|
GHSA-v3q9-2p3m-7g43
|
Token reuse in github.com/ory/fosite
|
### Impact
When using client authentication method "private_key_jwt" [1], OpenId specification says the following about assertion `jti`:
> A unique identifier for the token, which can be used to prevent reuse of the token. These tokens MUST only be used once, unless conditions for reuse were negotiated between the parties
Hydra does not seem to check the uniqueness of this `jti` value. Here is me sending the same token request twice, hence with the same `jti` assertion, and getting two access tokens:
```
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"zeG0NoqOtlACl8q5J6A-TIsNegQRRUzqLZaYrQtoBZQ.VR6iUcJQYp3u_j7pwvL7YtPqGhtyQe5OhnBE2KCp5pM","expires_in":3599,"scope":"application openid","token_type":"bearer"}⏎
$ curl --insecure --location --request POST 'https://localhost/_/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=c001d00d-5ecc-beef-ca4e-b00b1e54a111' \
--data-urlencode 'scope=application openid' \
--data-urlencode 'client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer' \
--data-urlencode 'client_assertion=eyJhb [...] jTw'
{"access_token":"wOYtgCLxLXlELORrwZlmeiqqMQ4kRzV-STU2_Sollas.mwlQGCZWXN7G2IoegUe1P0Vw5iGoKrkOzOaplhMSjm4","expires_in":3599,"scope":"application openid","token_type":"bearer"}
```
### Patches
_Has the problem been patched? What versions should users upgrade to?_
### Workarounds
Do not allow clients to use `private_key_jwt`.
### References
https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
|
{'CVE-2020-15222'}
|
2021-11-19T15:24:07Z
|
2021-05-24T16:57:52Z
|
HIGH
| 8.1
|
{'CWE-287', 'CWE-345'}
|
{'https://github.com/ory/fosite/commit/0c9e0f6d654913ad57c507dd9a36631e1858a3e9', 'https://github.com/ory/fosite/releases/tag/v0.31.0', 'https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication', 'https://github.com/ory/fosite/security/advisories/GHSA-v3q9-2p3m-7g43', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15222', 'https://github.com/advisories/GHSA-v3q9-2p3m-7g43'}
| null |
GHSA
|
GHSA-hwfp-hg2m-9vr2
|
Integer overflow in pywin32
|
An integer overflow exists in pywin32 prior to version b301 when adding an access control entry (ACE) to an access control list (ACL) that would cause the size to be greater than 65535 bytes. An attacker who successfully exploited this vulnerability could crash the vulnerable process.
|
{'CVE-2021-32559'}
|
2021-08-09T20:43:44Z
|
2021-08-09T20:43:44Z
|
MODERATE
| 6.5
|
{'CWE-190'}
|
{'https://github.com/fireeye/Vulnerability-Disclosures/blob/master/FEYE-2021-0017/FEYE-2021-0017.md', 'https://github.com/mhammond/pywin32/issues/1700', 'https://github.com/mhammond/pywin32/releases', 'https://github.com/mhammond/pywin32/pull/1701', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32559', 'https://github.com/advisories/GHSA-hwfp-hg2m-9vr2'}
| null |
GHSA
|
GHSA-4c87-gg2q-fc6m
|
Malicious Package in rc-calendar-jhorst
|
Version 8.4.3 of `rc-calendar-jhorst` 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
If version 8.4.3 of this module is found installed you will want to replace it with a version before or after 8.4.3. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.
| null |
2020-09-01T20:31:04Z
|
2020-09-01T20:31:04Z
|
CRITICAL
| 0
| null |
{'https://www.npmjs.com/advisories/633', 'https://github.com/advisories/GHSA-4c87-gg2q-fc6m'}
| null |
GHSA
|
GHSA-69mv-3642-wj3w
|
Low severity vulnerability that affects sensu
|
The sensu rubygem prior to version 1.2.0 contains a CWE-522 (Insufficiently Protected Credentials) flaw that can result in sensitive configuration data (e.g. passwords) being logged in clear-text.
Users are advised to upgrade to rubygem version 1.2.1 or later.
|
{'CVE-2018-1000060'}
|
2021-12-02T22:56:27Z
|
2018-07-23T19:50:22Z
|
LOW
| 0
| null |
{'https://github.com/sensu/sensu/issues/1804', 'https://github.com/sensu/sensu/pull/1810', 'https://github.com/advisories/GHSA-69mv-3642-wj3w', 'https://access.redhat.com/errata/RHSA-2018:1112', 'https://access.redhat.com/errata/RHSA-2018:1606', 'https://nvd.nist.gov/vuln/detail/CVE-2018-1000060', 'https://access.redhat.com/errata/RHSA-2018:0616'}
| null |
GHSA
|
GHSA-5vq5-pg3r-9ph3
|
Path Traversal in Zope
|
Zope is an open-source web application server. This advisory extends the previous advisory at https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36 with additional cases of TAL expression traversal vulnerabilities. Most Python modules are not available for using in TAL expressions that you can add through-the-web, for example in Zope Page Templates. This restriction avoids file system access, for example via the 'os' module. But some of the untrusted modules are available indirectly through Python modules that are available for direct use. By default, you need to have the Manager role to add or edit Zope Page Templates through the web. Only sites that allow untrusted users to add/edit Zope Page Templates through the web are at risk. The problem has been fixed in Zope 5.2.1 and 4.6.1. The workaround is the same as for https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36: A site administrator can restrict adding/editing Zope Page Templates through the web using the standard Zope user/role permission mechanisms. Untrusted users should not be assigned the Zope Manager role and adding/editing Zope Page Templates through the web should be restricted to trusted users only.
|
{'CVE-2021-32674'}
|
2022-01-03T15:56:18Z
|
2021-06-10T17:22:08Z
|
HIGH
| 8.8
|
{'CWE-12', 'CWE-22'}
|
{'https://github.com/zopefoundation/Zope/security/advisories/GHSA-rpcg-f9q6-2mq6', 'https://github.com/zopefoundation/Zope/commit/1d897910139e2c0b11984fc9b78c1da1365bec21', 'https://github.com/zopefoundation/Zope/security/advisories/GHSA-5pr9-v234-jw36', 'https://github.com/advisories/GHSA-5vq5-pg3r-9ph3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32674', 'https://pypi.org/project/Zope/'}
| null |
GHSA
|
GHSA-5h7w-hmxc-99g5
|
Cross site scripting in safe-svg
|
The sanitisation step of the Safe SVG WordPress plugin before 1.9.10 can be bypassed by spoofing the content-type in the POST request to upload a file. Exploiting this vulnerability, an attacker will be able to perform the kinds of attacks that this plugin should prevent (mainly XSS, but depending on further use of uploaded SVG files potentially other XML attacks).
|
{'CVE-2022-1091'}
|
2022-04-28T21:15:03Z
|
2022-04-19T00:00:45Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://wpscan.com/vulnerability/4d12533e-bdb7-411f-bcdf-4c5046db13f3', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1091', 'https://github.com/advisories/GHSA-5h7w-hmxc-99g5', 'https://github.com/10up/safe-svg/pull/28'}
| null |
GHSA
|
GHSA-pmpr-vc5q-h3jw
|
Exposure of Resource to Wrong Sphere in valib
|
valib through 2.0.0 allows Internal Property Tampering. A maliciously crafted JavaScript object can bypass several inspection functions provided by valib. Valib uses a built-in function (hasOwnProperty) from the unsafe user-input to examine an object. It is possible for a crafted payload to overwrite this function to manipulate the inspection results to bypass security checks.
|
{'CVE-2019-10805'}
|
2021-04-13T15:21:59Z
|
2021-04-13T15:21:59Z
|
MODERATE
| 7.5
|
{'CWE-668'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-10805', 'https://github.com/advisories/GHSA-pmpr-vc5q-h3jw', 'https://www.npmjs.com/package/valib', 'https://snyk.io/vuln/SNYK-JS-VALIB-559015'}
| null |
GHSA
|
GHSA-g3vv-g2j5-45f2
|
Panic when processing certain blocks
|
### Impact
Decoding certain blocks using the go-ipld-prime version of the dag-pb codec (go-codec-dagpb) can cause a panic. The panic comes from an assumption that the reported link length is accurate, but if the block ends before that reported length then it’s a buffer overread.
### Patches
The issue is fixed in v1.3.1 and above.
Consumers can discover the versions of `go-codec-dagpb` in a module's dependency graph using the following command in the module root:
```go mod graph | grep go-codec-dagpb```
### Workarounds
You can work around this issue without upgrading by recovering panics higher in the call stack of the goroutine that calls the defective code.
### For more information
If you have any questions or comments about this advisory:
* Ask in [IPFS Discord #ipld-chatter](https://discord.gg/ipfs)
* Open an issue in [go-codec-dagpb](https://github.com/ipld/go-codec-dagpb)
| null |
2022-04-12T21:41:41Z
|
2022-04-08T22:08:45Z
|
MODERATE
| 0
| null |
{'https://github.com/ipld/go-codec-dagpb/security/advisories/GHSA-g3vv-g2j5-45f2', 'https://github.com/advisories/GHSA-g3vv-g2j5-45f2'}
| null |
GHSA
|
GHSA-pp7h-53gx-mx7r
|
Remote Memory Exposure in bl
|
A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls.
|
{'CVE-2020-8244'}
|
2021-05-10T16:25:30Z
|
2020-09-02T15:26:19Z
|
HIGH
| 6.5
|
{'CWE-126', 'CWE-125'}
|
{'https://github.com/rvagg/bl/commit/d3e240e3b8ba4048d3c76ef5fb9dd1f8872d3190', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8244', 'https://github.com/rvagg/bl/commit/dacc4ac7d5fcd6201bcf26fbd886951be9537466', 'https://hackerone.com/reports/966347', 'https://github.com/advisories/GHSA-pp7h-53gx-mx7r', 'https://github.com/rvagg/bl/commit/8a8c13c880e2bef519133ea43e0e9b78b5d0c91e'}
| null |
GHSA
|
GHSA-92w9-2pqw-rhjj
|
Moderate severity vulnerability that affects actionpack
|
The decode_credentials method in actionpack/lib/action_controller/metal/http_authentication.rb in Ruby on Rails 3.x before 3.0.16, 3.1.x before 3.1.7, and 3.2.x before 3.2.7 converts Digest Authentication strings to symbols, which allows remote attackers to cause a denial of service by leveraging access to an application that uses a with_http_digest helper method, as demonstrated by the authenticate_or_request_with_http_digest method.
|
{'CVE-2012-3424'}
|
2021-09-07T20:38:15Z
|
2017-10-24T18:33:38Z
|
MODERATE
| 0
|
{'CWE-287'}
|
{'https://github.com/advisories/GHSA-92w9-2pqw-rhjj', 'http://weblog.rubyonrails.org/2012/7/26/ann-rails-3-2-7-has-been-released/', 'https://nvd.nist.gov/vuln/detail/CVE-2012-3424', 'https://groups.google.com/group/rubyonrails-security/msg/244d32f2fa25147d?hl=en&dmode=source&output=gplain', 'http://lists.opensuse.org/opensuse-updates/2012-08/msg00046.html', 'http://rhn.redhat.com/errata/RHSA-2013-0154.html'}
| null |
GHSA
|
GHSA-7wgr-7666-7pwj
|
Path Traversal in openapi-python-client
|
### Impact
Path traversal vulnerability. If a user generated a client using a maliciously crafted OpenAPI document, it is possible for generated files to be placed in arbitrary locations on disk.
Giving this a CVSS score of 3.0 (Low) with CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:N/E:P/RL:U/RC:C
### Patches
A fix is being worked on for version 0.5.3
### Workarounds
Inspect OpenAPI documents before generating clients for them.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [openapi-python-client](https://github.com/triaxtec/openapi-python-client/issues)
* Email us at [danthony@triaxtec.com](mailto:danthony@triaxtec.com)
|
{'CVE-2020-15141'}
|
2022-04-19T19:02:33Z
|
2020-08-20T14:38:13Z
|
LOW
| 3
|
{'CWE-22'}
|
{'https://pypi.org/project/openapi-python-client', 'https://github.com/triaxtec/openapi-python-client/blob/main/CHANGELOG.md#053---2020-08-13', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15141', 'https://github.com/triaxtec/openapi-python-client/security/advisories/GHSA-7wgr-7666-7pwj', 'https://pypi.org/project/openapi-python-client/', 'https://github.com/advisories/GHSA-7wgr-7666-7pwj', 'https://github.com/triaxtec/openapi-python-client/commit/3e7dfae5d0b3685abf1ede1bc6c086a116ac4746'}
| null |
GHSA
|
GHSA-p9cm-r7jg-8q3g
|
Incorrect signature verification in SimpleSAMLphp
|
### Background
An incorrect check of return values in the signature validation utilities allows an attacker to get invalid signatures accepted as valid by forcing an error during validation.
### Description
The `SimpleSAML_XML_Validator` class allows the verification of the XML digital signature of a SAML 1 message with a given key. In particular, the constructor of the class receives an XML node and a key to verify it and throws an exception in case there is an error, either caused by incorrect input or an invalid signature. This method uses the `verify()` method from the `RobRichards\XMLSecDSig` class to verify the signature with the given key, which in turn will end up calling `openssl_verify()` depending on the signature algorithm used.
The `openssl_verify()` function returns `1` when the signature was successfully verified, `0` if it failed to verify with the given key and `-1` in case an error occurs. PHP allows translating numerical values to boolean implicitly, with the following correspondences:
- `0` equals `false`
- Non-zero equals `true`
This means that an implicit conversion to _boolean_ of the values returned by `openssl_verify()` will convert an error state, signaled by the value `-1`, to successful verification of the signature (represented by the _boolean_ `true`).
The aforementioned constructor was performing an implicit conversion to boolean of the values returned by the `verify()` method, which subsequently will return the same output as `openssl_verify()` under most circumstances. This means an error during signature verification is treated as a successful verification by the method.
### Affected versions
All SimpleSAMLphp versions prior to **1.14.11**.
### Impact
Upon successful exploitation, an invalid signature would be regarded as valid by an affected version of the software. This allows attackers to modify or manually craft **SAML 1 response messages** and, by triggering a signature validation error in the affected party, get those messages accepted as valid and coming from a trusted entity. In practice, this means full capabilities to impersonate any individual at a given service provider.
The issue can be exploited to get other invalid messages accepted as valid, though the security implications there are minor.
In order to exploit the issue, **SAML 1.1 metadata must be registered by the vulnerable Service Provider for the Identity Provider targeted by the attacker** (in `metadata/shib13-idp-remote.php`), and an incorrect context must be fed to the signature validation routines, or an exceptional error must be triggered. So far, the following cases have been identified:
- Using a DSA public key to validate an XML signature made with an RSA-related algorithm.
- Using an RSA public key to validate an XML signature made with a DSA-related algorithm.
- Exhausting available memory while verifying the signature.
SimpleSAMLphp **does not support DSA signatures or keys**. Therefore, it is not possible for an attacker to feed an incorrect context by sending a signature with an incorrect algorithm. Upon reception of a DSA-SHA1 signature, SimpleSAMLphp will refuse to perform the validation due to the algorithm not being supported. On the other hand, if an attacker manages to trick a service provider operator to change the public key associated to a certain IdP to a DSA key, signatures made with any combination of the RSA algorithm will be accepted, regardless of whether they are valid or not. This means some serious misconfiguration or social engineering is needed in this case for a successful attack.
Regarding memory exhaustion, it is in theory possible to attack a service provider causing the consumption of all available memory while a message with an invalid signature is being validated. However, memory exhaustion must happen only during signature validation and not immediately before or after. This means exploitation of this case is extremely difficult due to the small time window available for the attacker and the precise control that is needed over the service provider.
All in all, the consequences of this issue are critical, so even though we consider it difficult to exploit, and considering that other ways to trigger failures in signature validation could be possible but so far unidentified, we recommend updating the affected software as soon as possible.
### Resolution
Upgrade to the latest version.
### Credit
This security issue was discovered and reported on December 3, 2016 by Thijs Kinkhorst.
|
{'CVE-2016-9955'}
|
2022-04-19T19:02:23Z
|
2020-01-24T21:27:42Z
|
MODERATE
| 6.3
|
{'CWE-20'}
|
{'https://simplesamlphp.org/security/201612-02', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9955', 'https://github.com/advisories/GHSA-p9cm-r7jg-8q3g', 'http://www.securityfocus.com/bid/94946', 'https://lists.debian.org/debian-lts-announce/2018/03/msg00001.html', 'https://github.com/simplesamlphp/simplesamlphp/security/advisories/GHSA-p9cm-r7jg-8q3g'}
| null |
GHSA
|
GHSA-7r82-7xv7-xcpj
|
Cross-site scripting in Apache HttpClient
|
Apache HttpClient versions prior to version 4.5.13 and 5.0.3 can misinterpret malformed authority component in request URIs passed to the library as java.net.URI object and pick the wrong target host for request execution.
|
{'CVE-2020-13956'}
|
2022-04-22T17:22:17Z
|
2021-06-03T23:40:23Z
|
MODERATE
| 5.3
|
{'CWE-79'}
|
{'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.apache.org/thread.html/reef569c2419705754a3acf42b5f19b2a158153cef0e448158bc54917@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/ra8bc6b61c5df301a6fe5a716315528ecd17ccb8a7f907e24a47a1a5e@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/ree942561f4620313c75982a4e5f3b74fe6f7062b073210779648eec2@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/rb33212dab7beccaf1ffef9b88610047c644f644c7a0ebdc44d77e381@%3Ccommits.turbine.apache.org%3E', 'https://lists.apache.org/thread.html/rcd9ad5dda60c82ab0d0c9bd3e9cb1dc740804451fc20c7f451ef5cc4@%3Cgitbox.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r55b2a1d1e9b1ec9db792b93da8f0f99a4fd5a5310b02673359d9b4d1@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/rea3dbf633dde5008d38bf6600a3738b9216e733e03f9ff7becf79625@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r2835543ef0f91adcc47da72389b816e36936f584c7be584d2314fac3@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/rc5c6ccb86d2afe46bbd4b71573f0448dc1f87bbcd5a0d8c7f8f904b2@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/r0bebe6f9808ac7bdf572873b4fa96a29c6398c90dab29f131f3ebffe@%3Cissues.solr.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20220210-0002/', 'https://lists.apache.org/thread.html/r5fec9c1d67f928179adf484b01e7becd7c0a6fdfe3a08f92ea743b90@%3Cissues.hive.apache.org%3E', 'https://lists.apache.org/thread.html/rcced7ed3237c29cd19c1e9bf465d0038b8b2e967b99fc283db7ca553@%3Cdev.ranger.apache.org%3E', 'https://lists.apache.org/thread.html/r70c429923100c5a4fae8e5bc71c8a2d39af3de4888f50a0ac3755e6f@%3Ccommits.creadur.apache.org%3E', 'https://lists.apache.org/thread.html/rfc00884c7b7ca878297bffe45fcb742c362b00b26ba37070706d44c3@%3Cissues.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r5de3d3808e7b5028df966e45115e006456c4e8931dc1e29036f17927@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/rf7ca60f78f05b772cc07d27e31bcd112f9910a05caf9095e38ee150f@%3Cdev.ranger.apache.org%3E', 'https://lists.apache.org/thread.html/rad6222134183046f3928f733bf680919e0c390739bfbfe6c90049673@%3Cissues.drill.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/r043a75acdeb52b15dd5e9524cdadef4202e6a5228644206acf9363f9@%3Cdev.hive.apache.org%3E', 'https://lists.apache.org/thread.html/r5b55f65c123a7481104d663a915ec45a0d103e6aaa03f42ed1c07a89@%3Cdev.jackrabbit.apache.org%3E', 'https://lists.apache.org/thread.html/rf03228972e56cb4a03e6d9558188c2938078cf3ceb23a3fead87c9ca@%3Cissues.bookkeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r3cecd59fba74404cbf4eb430135e1080897fb376f111406a78bed13a@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26@%3Ccommits.pulsar.apache.org%3E', 'https://lists.apache.org/thread.html/rf4db88c22e1be9eb60c7dc623d0528642c045fb196a24774ac2fa3a3@%3Cissues.lucene.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r12cb62751b35bdcda0ae2a08b67877d665a1f4d41eee0fa7367169e0@%3Cdev.ranger.apache.org%3E', 'https://lists.apache.org/thread.html/rfb35f6db9ba1f1e061b63769a4eff5abadcc254ebfefc280e5a0dcf1@%3Ccommits.creadur.apache.org%3E', 'https://lists.apache.org/thread.html/r9e52a6c72c8365000ecd035e48cc9fee5a677a150350d4420c46443d@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r3f740e4c38bba1face49078aa5cbeeb558c27be601cc9712ad2dcd1e@%3Ccommits.creadur.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2020-13956', 'https://lists.apache.org/thread.html/rc3739e0ad4bcf1888c6925233bfc37dd71156bbc8416604833095c42@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/ra539f20ef0fb0c27ee39945b5f56bf162e5c13d1c60f7344dab8de3b@%3Cissues.maven.apache.org%3E', 'https://lists.apache.org/thread.html/r4850b3fbaea02fde2886e461005e4af8d37c80a48b3ce2a6edca0e30@%3Cissues.solr.apache.org%3E', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.apache.org/thread.html/rc505fee574fe8d18f9b0c655a4d120b0ae21bb6a73b96003e1d9be35@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r2a03dc210231d7e852ef73015f71792ac0fcaca6cccc024c522ef17d@%3Ccommits.creadur.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'https://lists.apache.org/thread.html/r34178ab6ef106bc940665fd3f4ba5026fac3603b3fa2aefafa0b619d@%3Cdev.ranger.apache.org%3E', 'https://lists.apache.org/thread.html/rd5ab56beb2ac6879f6ab427bc4e5f7691aed8362d17b713f61779858@%3Cissues.hive.apache.org%3E', 'https://lists.apache.org/thread.html/rc0863892ccfd9fd0d0ae10091f24ee769fb39b8957fe4ebabfc11f17@%3Cdev.jackrabbit.apache.org%3E', 'https://lists.apache.org/thread.html/r63296c45d5d84447babaf39bd1487329d8a80d8d563e67a4b6f3d8a7@%3Cdev.ranger.apache.org%3E', 'https://lists.apache.org/thread.html/r2dc7930b43eadc78220d269b79e13ecd387e4bee52db67b2f47d4303@%3Cgitbox.hive.apache.org%3E', 'https://lists.apache.org/thread.html/rb4ba262d6f08ab9cf8b1ebbcd9b00b0368ffe90dad7ad7918b4b56fc@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/rfbedcb586a1e7dfce87ee03c720e583fc2ceeafa05f35c542cecc624@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r69a94e2f302d1b778bdfefe90fcb4b8c50b226438c3c8c1d0de85a19@%3Cdev.ranger.apache.org%3E', 'https://github.com/advisories/GHSA-7r82-7xv7-xcpj', 'https://lists.apache.org/thread.html/r549ac8c159bf0c568c19670bedeb8d7c0074beded951d34b1c1d0d05@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/rae14ae25ff4a60251e3ba2629c082c5ba3851dfd4d21218b99b56652@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r34efec51cb817397ccf9f86e25a75676d435ba5f83ee7b2eabdad707@%3Ccommits.creadur.apache.org%3E', 'https://lists.apache.org/thread.html/r0a75b8f0f72f3e18442dc56d33f3827b905f2fe5b7ba48997436f5d1@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r6d672b46622842e565e00f6ef6bef83eb55d8792aac2bee75bff9a2a@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/rc990e2462ec32b09523deafb2c73606208599e196fa2d7f50bdbc587@%3Cissues.maven.apache.org%3E', 'https://lists.apache.org/thread.html/r03bbc318c81be21f5c8a9b85e34f2ecc741aa804a8e43b0ef2c37749@%3Cissues.maven.apache.org%3E', 'https://lists.apache.org/thread.html/r6a3cda38d050ebe13c1bc9a28d0a8ec38945095d07eca49046bcb89f@%3Cissues.solr.apache.org%3E', 'https://lists.apache.org/thread.html/r6dab7da30f8bf075f79ee189e33b45a197502e2676481bb8787fc0d7%40%3Cdev.hc.apache.org%3E', 'https://lists.apache.org/thread.html/r132e4c6a560cfc519caa1aaee63bdd4036327610eadbd89f76dd5457@%3Cdev.creadur.apache.org%3E', 'https://lists.apache.org/thread.html/rf43d17ed0d1fb4fb79036b582810ef60b18b1ef3add0d5dea825af1e@%3Cissues.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/rb725052404fabffbe093c83b2c46f3f87e12c3193a82379afbc529f8@%3Csolr-user.lucene.apache.org%3E', 'https://lists.apache.org/thread.html/r87ddc09295c27f25471269ad0a79433a91224045988b88f0413a97ec@%3Cissues.bookkeeper.apache.org%3E', 'https://lists.apache.org/thread.html/r06cf3ca5c8ceb94b39cd24a73d4e96153b485a7dac88444dd876accb@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r6eb2dae157dbc9af1f30d1f64e9c60d4ebef618f3dce4a0e32d6ea4d@%3Ccommits.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r8aa1e5c343b89aec5b69961471950e862f15246cb6392910161c389b@%3Cissues.maven.apache.org%3E', 'https://lists.apache.org/thread.html/re504acd4d63b8df2a7353658f45c9a3137e5f80e41cf7de50058b2c1@%3Cissues.solr.apache.org%3E'}
| null |
GHSA
|
GHSA-vh8f-xw5v-8993
|
Command Injection in macfromip
|
All versions of npm package macfromip are affected by a command injection vulnerability. The injection point is located in line 66 in macfromip.js.
|
{'CVE-2020-7786'}
|
2021-04-12T19:01:26Z
|
2021-04-12T19:01:20Z
|
CRITICAL
| 9.8
|
{'CWE-74'}
|
{'https://www.npmjs.com/package/macfromip', 'https://github.com/advisories/GHSA-vh8f-xw5v-8993', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7786', 'https://snyk.io/vuln/SNYK-JS-MACFROMIP-1048336'}
| null |
GHSA
|
GHSA-gqpw-9q54-9x28
|
Server-Side Request Forgery in Concrete CMS
|
Concrete CMS (formerly concrete5) versions 8.5.6 and below and version 9.0.0 allow local IP importing causing the system to be vulnerable to SSRF attacks on the private LAN to servers by reading files from the local LAN. An attacker can pivot in the private LAN and exploit local network appsandb.
|
{'CVE-2021-22970'}
|
2021-11-23T18:18:43Z
|
2021-11-23T18:18:43Z
|
MODERATE
| 0
|
{'CWE-918'}
|
{'https://documentation.concretecms.org/developers/introduction/version-history/901-release-notes', 'https://github.com/advisories/GHSA-gqpw-9q54-9x28', 'https://hackerone.com/reports/1364797', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22970', 'https://documentation.concretecms.org/developers/introduction/version-history/857-release-notes'}
| null |
GHSA
|
GHSA-m496-x567-f98c
|
Fixes a bug in Zend Framework's Stream HTTP Wrapper
|
### Impact
CVE-2021-3007: Backport of Zend_Http_Response_Stream, added certain type checking as a way to prevent exploitation. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3007
This vulnerability is caused by the unsecured deserialization of an object. In versions higher than Zend Framework 3.0.0, the attacker abuses the Zend3 feature that loads classes from objects in order to upload and execute malicious code in the server. The code can be uploaded using the “callback” parameter, which in this case inserts a malicious code instead of the “callbackOptions” array.
### Patches
_Has the problem been patched? What versions should users upgrade to?_
v20.0.9 v19.4.13
|
{'CVE-2021-21426'}
|
2021-04-30T20:19:59Z
|
2021-04-22T16:10:49Z
|
CRITICAL
| 9.8
|
{'CWE-502'}
|
{'https://github.com/advisories/GHSA-m496-x567-f98c', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21426', 'https://github.com/OpenMage/magento-lts/security/advisories/GHSA-m496-x567-f98c'}
| null |
GHSA
|
GHSA-mxmj-84q8-34r7
|
Command Injection in expressfs
|
All versions of `expressfs` are vulnerable to Command Injection. The package does not validate user input on several API endpoints, allowing attackers to run arbitrary commands in the system. The affected endpoints are: `expressfs.appendFile`, `expressfs.cp`, `expressfs.create` and `expressfs.rmdir`.
## Recommendation
No fix is currently available. Consider using an alternative module until a fix is made available.
| null |
2021-09-28T13:56:56Z
|
2020-09-03T02:39:49Z
|
HIGH
| 0
|
{'CWE-77'}
|
{'https://github.com/advisories/GHSA-mxmj-84q8-34r7', 'https://www.npmjs.com/advisories/953'}
| null |
GHSA
|
GHSA-7cjc-hvxf-gqh7
|
Use after free and double free in bitvec
|
An issue was discovered in the bitvec crate before 0.17.4 for Rust. BitVec to BitBox conversion leads to a use-after-free or double free.
|
{'CVE-2020-35862'}
|
2021-08-25T20:47:39Z
|
2021-08-25T20:47:39Z
|
CRITICAL
| 9.8
|
{'CWE-415', 'CWE-416'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-35862', 'https://github.com/advisories/GHSA-7cjc-hvxf-gqh7', 'https://rustsec.org/advisories/RUSTSEC-2020-0007.html', 'https://github.com/myrrlyn/bitvec/issues/55'}
| null |
GHSA
|
GHSA-c8h6-89q2-mgv8
|
Malicious Package in dossier
|
Version 0.0.4 of `dossier` 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
If version 0.0.4 of this module is found installed you will want to replace it with a version before or after 0.0.4. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.
| null |
2021-09-24T17:24:28Z
|
2020-09-01T19:55:48Z
|
CRITICAL
| 9.8
|
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/625', 'https://github.com/advisories/GHSA-c8h6-89q2-mgv8', 'https://snyk.io/vuln/SNYK-JS-DOSSIER-450994'}
| null |
GHSA
|
GHSA-2r7f-4h2c-5x73
|
Arbitrary File Read in fury-adapter-swagger
|
Affected versions of `fury-adapter-swagger` have a weakness that allows an attacker to read arbitrary files off of the system. This can be used to read sensitive data, or to cause a denial of service condition by attempting to read something like `/dev/zero`.
## Proof of Concept:
```
---
swagger: '2.0'
info:
title: Read local files
version: '1.0'
paths:
/foo:
get:
responses:
200:
description: Some description
examples:
text/html:
example:
$ref: '/etc/passwd'
```
## Recommendation
Upgrade to version 0.9.7 or later
|
{'CVE-2016-1000249'}
|
2021-09-23T21:39:19Z
|
2020-09-01T16:38:33Z
|
CRITICAL
| 0
| null |
{'https://github.com/advisories/GHSA-2r7f-4h2c-5x73', 'https://www.npmjs.com/advisories/305'}
| null |
GHSA
|
GHSA-mw3r-pfmg-xp92
|
Improper Restriction of Recursive Entity References in Apache XMLBeans
|
The XML parsers used by XMLBeans up to version 2.6.0 did not set the properties needed to protect the user from malicious XML input. Vulnerabilities include possibilities for XML Entity Expansion attacks. Affects XMLBeans up to and including v2.6.0.
|
{'CVE-2021-23926'}
|
2021-10-21T18:58:59Z
|
2021-06-16T17:37:11Z
|
CRITICAL
| 9.1
|
{'CWE-776'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-23926', 'https://security.netapp.com/advisory/ntap-20210513-0004/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://issues.apache.org/jira/browse/XMLBEANS-517', 'https://lists.apache.org/thread.html/rbb01d10512098894cd5f22325588197532c64f1c818ea7e4120d40c1@%3Cjava-dev.axis.apache.org%3E', 'https://poi.apache.org/', 'https://lists.debian.org/debian-lts-announce/2021/06/msg00024.html', 'https://github.com/advisories/GHSA-mw3r-pfmg-xp92', 'https://lists.apache.org/thread.html/r2dc5588009dc9f0310b7382269f932cc96cae4c3901b747dda1a7fed@%3Cjava-dev.axis.apache.org%3E'}
| null |
GHSA
|
GHSA-7v7w-f7c6-f829
|
yetiforcecrm is vulnerable to Business Logic Errors
|
yetiforcecrm is vulnerable to Business Logic Errors.
|
{'CVE-2021-4111'}
|
2022-01-03T15:47:59Z
|
2021-12-16T21:01:15Z
|
HIGH
| 7.3
| null |
{'https://nvd.nist.gov/vuln/detail/CVE-2021-4111', 'https://huntr.dev/bounties/8afc8981-baff-4082-b640-be535b29eb9a', 'https://github.com/yetiforcecompany/yetiforcecrm/commit/c1ad7111a090adfcd5898af40724907adc987acf', 'https://github.com/advisories/GHSA-7v7w-f7c6-f829'}
| null |
GHSA
|
GHSA-jr9p-r423-9m2r
|
Vulnerability in markdown2
|
markdown2 >=1.0.1.18, fixed in 2.4.0, is affected by a regular expression denial of service vulnerability. If an attacker provides a malicious string, it can make markdown2 processing difficult or delayed for an extended period of time.
|
{'CVE-2021-26813'}
|
2021-09-30T16:49:22Z
|
2021-06-02T21:44:28Z
|
HIGH
| 7.5
| null |
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JTIX5UXRDJZJ57DO4V33ZNJTNKWGBQLY/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J752422YELXLMLZJPVJVKD2KKHHQRVEH/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BRP5RN35JZTSJ3JT4722F447ZDK7LZS5/', 'https://github.com/advisories/GHSA-jr9p-r423-9m2r', 'https://github.com/trentm/python-markdown2/pull/387', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26813'}
| null |
GHSA
|
GHSA-952p-fqcp-g8pc
|
HTML injection possibility in voucher code form in Shopware
|
### Impact
HTML injection possibility in voucher code form
## Patches
Patched in 6.4.8.1, maintainers recommend updating to the current version 6.4.8.2. You can get the update to 6.4.8.2 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, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
|
{'CVE-2022-24746'}
|
2022-03-18T20:14:16Z
|
2022-03-10T17:49:26Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://github.com/shopware/platform/commit/651598a61073cbe59368e311817bdc6e7fb349c6', 'https://github.com/shopware/platform/security/advisories/GHSA-952p-fqcp-g8pc', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2022?category=security-updates', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-02-2022', 'https://github.com/advisories/GHSA-952p-fqcp-g8pc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24746'}
| null |
GHSA
|
GHSA-5634-rv46-48jf
|
Cross-Site Scripting in bleach
|
All versions of `bleach` are vulnerable to Cross-Site Scripting. It is possible to bypass the package's HTML sanitization with payloads such as `"<<script><</script>script>alert('xss');</<script><</script>script>"` regardless of the passed options. This may allow attackers to execute arbitrary JavaScript in the victim's browser.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
| null |
2021-09-28T21:54:20Z
|
2020-09-03T17:13:45Z
|
HIGH
| 0
|
{'CWE-79'}
|
{'https://www.npmjs.com/advisories/1034', 'https://github.com/advisories/GHSA-5634-rv46-48jf'}
| null |
GHSA
|
GHSA-jhj6-5mh6-4pvf
|
Denial-of-Service within Docker container
|
### Impact
If you run teler inside a Docker container and encounter `errors.Exit` function, it will cause denial-of-service (`SIGSEGV`) because it doesn't get process ID and process group ID of teler properly to kills.
### Patches
Upgrade to the >= 0.0.1 version.
### Workarounds
N/A
### References
- https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [Issues Section](https://github.com/kitabisa/teler/issues)
* Email us at [infosec@kitabisa.com](mailto:infosec@kitabisa.com)
|
{'CVE-2020-26213'}
|
2021-10-11T21:06:20Z
|
2021-05-24T17:00:46Z
|
MODERATE
| 7.5
|
{'CWE-476'}
|
{'https://github.com/kitabisa/teler/security/advisories/GHSA-jhj6-5mh6-4pvf', 'https://github.com/advisories/GHSA-jhj6-5mh6-4pvf', 'https://github.com/kitabisa/teler/commit/ec6082049dba9e44a21f35fb7b123d42ce1a1a7e', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26213'}
| null |
GHSA
|
GHSA-v3f6-f29f-rgvp
|
Missing Authorization in Drupal
|
In Drupal 8.x prior to 8.3.7 When creating a view, you can optionally use Ajax to update the displayed data via filter parameters. The views subsystem/module did not restrict access to the Ajax endpoint to only views configured to use Ajax. This is mitigated if you have access restrictions on the view. It is best practice to always include some form of access restrictions on all views, even if you are using another module to display them.
|
{'CVE-2017-6923'}
|
2021-08-18T21:44:06Z
|
2019-10-10T19:31:31Z
|
MODERATE
| 6.5
|
{'CWE-862'}
|
{'https://www.drupal.org/forum/newsletters/security-advisories-for-drupal-core/2017-08-16/drupal-core-multiple', 'http://www.securityfocus.com/bid/100368', 'http://www.securitytracker.com/id/1039200', 'https://nvd.nist.gov/vuln/detail/CVE-2017-6923', 'https://github.com/advisories/GHSA-v3f6-f29f-rgvp'}
| null |
GHSA
|
GHSA-45q2-34rf-mr94
|
Code Injection in mquery
|
lib/utils.js in mquery before 3.2.3 allows a pollution attack because a special property (e.g., __proto__) can be copied during a merge or clone operation.
|
{'CVE-2020-35149'}
|
2020-12-18T18:23:43Z
|
2020-12-18T18:23:43Z
|
MODERATE
| 5.3
|
{'CWE-94'}
|
{'https://github.com/advisories/GHSA-45q2-34rf-mr94', 'https://nvd.nist.gov/vuln/detail/CVE-2020-35149', 'https://github.com/aheckmann/mquery/commit/792e69fd0a7281a0300be5cade5a6d7c1d468ad4'}
| null |
GHSA
|
GHSA-gpmh-g94g-qrhr
|
Internal hidden fields are visible on to many associations in admin api
|
### Impact
The admin api has exposed some internal hidden fields when an association has been loaded with a to many reference
### Patches
We recommend updating to the current version 6.4.1.1. You can get the update to 6.4.1.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, 6.2, and 6.3, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.
https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659
| null |
2021-06-28T18:20:53Z
|
2021-06-28T18:20:53Z
|
MODERATE
| 0
| null |
{'https://github.com/shopware/platform/security/advisories/GHSA-gpmh-g94g-qrhr', 'https://github.com/advisories/GHSA-gpmh-g94g-qrhr'}
| null |
GHSA
|
GHSA-9wx7-jrvc-28mm
|
Signature verification vulnerability in Stark Bank ecdsa libraries
|
An attacker can forge signatures on arbitrary messages that will verify for any public key. This may allow attackers to authenticate as any user within the Stark Bank platform, and bypass signature verification needed to perform operations on the platform, such as send payments and transfer funds. Additionally, the ability for attackers to forge signatures may impact other users and projects using these libraries in different and unforeseen ways.
| null |
2021-11-08T21:51:18Z
|
2021-11-08T21:51:18Z
|
HIGH
| 0
|
{'CWE-347'}
|
{'https://research.nccgroup.com/2021/11/08/technical-advisory-arbitrary-signature-forgery-in-stark-bank-ecdsa-libraries/', 'https://github.com/starkbank/ecdsa-python/releases/tag/v2.0.1', 'https://github.com/starkbank/ecdsa-node', 'https://github.com/starkbank/ecdsa-dotnet', 'https://github.com/starkbank/ecdsa-java', 'https://github.com/advisories/GHSA-9wx7-jrvc-28mm'}
| null |
GHSA
|
GHSA-77rm-9x9h-xj3g
|
NULL Pointer Dereference in Protocol Buffers
|
Nullptr dereference when a null char is present in a proto symbol. The symbol is parsed incorrectly, leading to an unchecked call into the proto file's name during generation of the resulting error message. Since the symbol is incorrectly parsed, the file is nullptr. We recommend upgrading to version 3.15.0 or greater.
|
{'CVE-2021-22570'}
|
2022-05-03T03:47:53Z
|
2022-01-27T00:01:15Z
|
HIGH
| 7.5
|
{'CWE-476'}
|
{'https://github.com/advisories/GHSA-77rm-9x9h-xj3g', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22570', 'https://www.oracle.com/security-alerts/cpuapr2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BTRGBRC5KGCA4SK5MUNLPYJRAGXMBIYY/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KQJB6ZPRLKV6WCMX2PRRRQBFAOXFBK6B/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NVTWVQRB5OCCTMKEQFY5MYED3DXDVSLP/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5PAGL5M2KGYPN3VEQCRJJE6NA7D5YG5X/', 'https://github.com/protocolbuffers/protobuf/releases/tag/v3.15.0', 'https://security.netapp.com/advisory/ntap-20220429-0005/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MRWRAXAFR3JR7XCFWTHC2KALSZKWACCE/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3DVUZPALAQ34TQP6KFNLM4IZS6B32XSA/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IFX6KPNOFHYD6L4XES5PCM3QNSKZBOTQ/'}
| null |
GHSA
|
GHSA-9735-p6r2-2hgh
|
Out-of-bounds write
|
A remote code execution vulnerability exists in the way the scripting engine handles objects in memory in Microsoft browsers, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0884, CVE-2019-0918.
|
{'CVE-2019-0911'}
|
2021-03-29T21:00:00Z
|
2021-03-29T21:00:00Z
|
HIGH
| 7.5
|
{'CWE-787'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-0911', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0911', 'https://github.com/advisories/GHSA-9735-p6r2-2hgh', 'https://github.com/chakra-core/ChakraCore/commit/d797e3f00e34c12c8c0ae52f56344325439dccd7', 'https://github.com/chakra-core/ChakraCore/commit/a2deba5e1850782014a2a34678464b251e448337'}
| null |
GHSA
|
GHSA-mjxr-4v3x-q3m4
|
Improper Input Validation in sanitize-html
|
Apostrophe Technologies sanitize-html before 2.3.2 does not properly validate the hostnames set by the "allowedIframeHostnames" option when the "allowIframeRelativeUrls" is set to true, which allows attackers to bypass hostname whitelist for iframe element, related using an src value that starts with "/\\example.com".
|
{'CVE-2021-26540'}
|
2021-05-06T16:10:19Z
|
2021-05-06T16:10:19Z
|
MODERATE
| 5.3
|
{'CWE-20'}
|
{'https://advisory.checkmarx.net/advisory/CX-2021-4309', 'https://github.com/apostrophecms/sanitize-html/blob/main/CHANGELOG.md#232-2021-01-26', 'https://github.com/apostrophecms/sanitize-html/pull/460', 'https://github.com/advisories/GHSA-mjxr-4v3x-q3m4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-26540'}
| null |
GHSA
|
GHSA-cj78-rgw3-4h5p
|
Improper Restriction of XML External Entity Reference in trytond and proteus
|
An XXE issue was discovered in Tryton Application Platform (Server) 5.x through 5.0.45, 6.x through 6.0.15, and 6.1.x and 6.2.x through 6.2.5, and Tryton Application Platform (Command Line Client (proteus)) 5.x through 5.0.11, 6.x through 6.0.4, and 6.1.x and 6.2.x through 6.2.1. An authenticated user can make the server parse a crafted XML SEPA file to access arbitrary files on the system.
|
{'CVE-2022-26661'}
|
2022-03-29T21:02:33Z
|
2022-03-11T00:02:02Z
|
MODERATE
| 6.5
|
{'CWE-611'}
|
{'https://discuss.tryton.org/t/security-release-for-issue11219-and-issue11244/5059', 'https://www.debian.org/security/2022/dsa-5099', 'https://bugs.tryton.org/issue11219', 'https://nvd.nist.gov/vuln/detail/CVE-2022-26661', 'https://github.com/advisories/GHSA-cj78-rgw3-4h5p', 'https://www.debian.org/security/2022/dsa-5098', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00016.html', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00017.html'}
| null |
GHSA
|
GHSA-f757-9c4x-chff
|
Downloads Resources over HTTP in poco
|
Affected versions of `poco` 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 `poco`.
## 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-10659'}
|
2021-01-08T18:54:12Z
|
2019-02-18T23:54:44Z
|
HIGH
| 0
|
{'CWE-311'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2016-10659', 'https://www.npmjs.com/advisories/271', 'https://nodesecurity.io/advisories/271', 'https://github.com/advisories/GHSA-f757-9c4x-chff'}
| null |
GHSA
|
GHSA-c38g-469g-cmgx
|
"Improper Neutralization of Special Elements in Output in helm.sh/helm/v3"
|
Since Helm 2 was released, a well-documented aspect of Helm is that the Helm chart's version number MUST follow the SemVer2 specification. In the past, Helm would not permit charts with malformed versions. At some point, a patch was merged that changed this - On a version parse error, the version number was simply passed along as-is. This provided a vector for malicious data to be injected into Helm and potentially used in various ways.
Core maintainers were able to send deceptive information to a terminal screen running the `helm` command, as well as obscure or alter information on the screen. In some cases, we could send codes that terminals used to execute higher-order logic, like clearing a terminal screen.
Further, during evaluation, the Helm maintainers discovered a few other fields that were not properly sanitized when read out of repository index files. This fix remedies all such cases, and once again enforces SemVer2 policies on version fields.
All users of the Helm 3 should upgrade.
Those who use Helm as a library should verify that they either sanitize this data on their own, or use the proper Helm API calls to sanitize the data.
### Patches
This issue has been resolved in Helm 3.5.1.
While this fix does not constitute a breaking change, as all field formatting is now enforced as documented, it is possible that charts that were mistakenly allowed (but invalid) may no longer be available in search indexes. Specifically, **malformed SemVer versions are no longer supported**. This has always been the documented case, but it is true that malformed versions were allowed.
Note that this is the first security release since Helm 2's final deprecation. Helm 2 was not audited for vulnerability to this issue, and should be assumed vulnerable.
|
{'CVE-2021-21303'}
|
2021-06-23T18:14:40Z
|
2021-06-23T18:14:40Z
|
MODERATE
| 5.9
|
{'CWE-74', 'CWE-20'}
|
{'https://github.com/helm/helm/commit/6ce9ba60b73013857e2e7c73d3f86ed70bc1ac9a', 'https://github.com/helm/helm/security/advisories/GHSA-c38g-469g-cmgx', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21303', 'https://github.com/advisories/GHSA-c38g-469g-cmgx', 'https://github.com/helm/helm/releases/tag/v3.5.2'}
| null |
GHSA
|
GHSA-9qj6-4rfq-vm84
|
Out-of-bounds Write in actix-web
|
An issue was discovered in the actix-web crate before 0.7.15 for Rust. It can unsoundly coerce an immutable reference into a mutable reference, leading to memory corruption.
|
{'CVE-2018-25024'}
|
2022-01-06T22:20:41Z
|
2022-01-06T22:20:41Z
|
CRITICAL
| 9.8
|
{'CWE-787'}
|
{'https://github.com/advisories/GHSA-9qj6-4rfq-vm84', 'https://nvd.nist.gov/vuln/detail/CVE-2018-25024', 'https://rustsec.org/advisories/RUSTSEC-2018-0019.html', 'https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/actix-web/RUSTSEC-2018-0019.md'}
| null |
GHSA
|
GHSA-9qgh-7pgp-hp7r
|
Cross-Site Scripting in graylog-web-interface
|
All versions of `graylog-web-interface` are vulnerable to Cross-Site Scripting (XSS). The package fails to escape output on the `TypeAhead` and `QueryInput` components, which may allow attackers to execute arbitrary JavaScript on the victim's browser.
## Recommendation
No fix is currently available. Consider using an alternative package until a fix is made available.
| null |
2021-09-28T21:18:39Z
|
2020-09-03T17:10:31Z
|
HIGH
| 0
|
{'CWE-79'}
|
{'https://www.npmjs.com/advisories/1028', 'https://github.com/advisories/GHSA-9qgh-7pgp-hp7r'}
| null |
GHSA
|
GHSA-733f-44f3-3frw
|
Open redirect
|
macaron before 1.3.7 has an open redirect in the static handler, as demonstrated by the http://127.0.0.1:4000//example.com/ URL.
|
{'CVE-2020-12666'}
|
2021-05-18T21:08:35Z
|
2021-05-18T21:08:35Z
|
MODERATE
| 6.1
|
{'CWE-601'}
|
{'https://github.com/go-macaron/macaron/pull/199/commits/6bd9385542f7133467ab7d09a5f28f7d5dc52af7', 'https://github.com/advisories/GHSA-733f-44f3-3frw', 'https://github.com/go-macaron/macaron/releases/tag/v1.3.7', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3QEUOHRC4EN4WZ66EVFML2UCV7ZQ63XZ/', 'https://github.com/go-macaron/macaron/issues/198#issuecomment-622885959', 'https://github.com/go-macaron/macaron/issues/198', 'https://nvd.nist.gov/vuln/detail/CVE-2020-12666'}
| null |
GHSA
|
GHSA-hxcm-v35h-mg2x
|
Prototype Pollution
|
A vulnerability was found in querystringify before 2.0.0. It's possible to override built-in properties of the resulting query string object if a malicious string is inserted in the query string.
| null |
2021-02-25T17:25:44Z
|
2019-06-07T21:12:50Z
|
HIGH
| 0
|
{'CWE-1312'}
|
{'https://github.com/unshiftio/querystringify/pull/19', 'https://github.com/advisories/GHSA-hxcm-v35h-mg2x', 'https://github.com/unshiftio/querystringify/commit/422eb4f6c7c28ee5f100dcc64177d3b68bb2b080'}
| null |
GHSA
|
GHSA-p7j5-4mwm-hv86
|
Cross-site scripting in TinyMCE
|
TinyMCE before 4.9.7 and 5.x before 5.1.4 allows XSS in the core parser, the paste plugin, and the visualchars plugin by using the clipboard or APIs to insert content into the editor.
|
{'CVE-2020-17480'}
|
2021-05-06T17:28:14Z
|
2021-05-06T17:28:14Z
|
MODERATE
| 6.1
|
{'CWE-79'}
|
{'https://www.tiny.cloud/docs/release-notes/release-notes514/#securityfixes', 'https://github.com/tinymce/tinymce/security/advisories/GHSA-27gm-ghr9-4v95', 'https://nvd.nist.gov/vuln/detail/CVE-2020-17480', 'https://github.com/advisories/GHSA-p7j5-4mwm-hv86'}
| null |
GHSA
|
GHSA-699q-wcff-g9mj
|
Unsafe deserialization in Yii 2
|
### Impact
Remote code execution in case application calls `unserialize()` on user input containing specially crafted string.
### Patches
2.0.38
### Workarounds
Add the following to BatchQueryResult.php:
```php
public function __sleep()
{
throw new \BadMethodCallException('Cannot serialize '.__CLASS__);
}
public function __wakeup()
{
throw new \BadMethodCallException('Cannot unserialize '.__CLASS__);
}
```
### For more information
If you have any questions or comments about this advisory, [contact us through security form](https://www.yiiframework.com/security).
|
{'CVE-2020-15148'}
|
2022-04-19T19:02:33Z
|
2020-09-15T18:19:56Z
|
HIGH
| 8.9
|
{'CWE-502'}
|
{'https://github.com/yiisoft/yii2/security/advisories/GHSA-699q-wcff-g9mj', 'https://github.com/advisories/GHSA-699q-wcff-g9mj', 'https://github.com/yiisoft/yii2/commit/9abccb96d7c5ddb569f92d1a748f50ee9b3e2b99', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15148'}
| null |
GHSA
|
GHSA-pcqq-5962-hvcw
|
Denial of Service in uap-core when processing crafted User-Agent strings
|
### Impact
Some regexes are vulnerable to regular expression denial of service (REDoS) due to overlapping capture groups. This allows remote attackers to overload a server by setting the User-Agent header in an HTTP(S) request to maliciously crafted long strings.
### Patches
Please update `uap-ruby` to >= v2.6.0
### For more information
https://github.com/ua-parser/uap-core/security/advisories/GHSA-cmcx-xhr8-3w9p
Reported in `uap-core` by Ben Caller @bcaller
| null |
2022-04-19T19:02:24Z
|
2020-03-10T18:02:49Z
|
HIGH
| 0
| null |
{'https://github.com/ua-parser/uap-ruby/commit/2bb18268f4c5ba7d4ba0e21c296bf6437063da3a', 'https://github.com/advisories/GHSA-pcqq-5962-hvcw', 'https://github.com/ua-parser/uap-ruby/security/advisories/GHSA-pcqq-5962-hvcw'}
| null |
GHSA
|
GHSA-5jxc-hmqf-3f73
|
Cross-Site Scripting in grav
|
grav prior to version 1.7.24 is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
|
{'CVE-2021-3904'}
|
2021-11-01T19:17:31Z
|
2021-11-01T19:17:31Z
|
MODERATE
| 6.3
|
{'CWE-79'}
|
{'https://github.com/advisories/GHSA-5jxc-hmqf-3f73', 'https://huntr.dev/bounties/b1182515-d911-4da9-b4f7-b4c341a62a8d', 'https://github.com/getgrav/grav/commit/afc69a3229bb6fe120b2c1ea27bc6f196ed7284d', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3904'}
| null |
GHSA
|
GHSA-xf5p-87ch-gxw2
|
Regular Expression Denial of Service in marked
|
Versions of `marked` prior to 0.6.2 and later than 0.3.14 are vulnerable to Regular Expression Denial of Service. Email addresses may be evaluated in quadratic time, allowing attackers to potentially crash the node process due to resource exhaustion.
## Recommendation
Upgrade to version 0.6.2 or later.
| null |
2021-08-04T20:53:01Z
|
2019-06-05T14:10:03Z
|
MODERATE
| 5.3
|
{'CWE-400'}
|
{'https://github.com/advisories/GHSA-xf5p-87ch-gxw2', 'https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d', 'https://github.com/markedjs/marked/pull/1460', 'https://www.npmjs.com/advisories/812', 'https://snyk.io/vuln/SNYK-JS-MARKED-174116', 'https://github.com/markedjs/marked/issues/1070'}
| null |
GHSA
|
GHSA-mcq2-w56r-5w2w
|
Daemon panics when processing certain blocks
|
### Impact
go-ipfs nodes with versions 0.10.0, 0.11.0, 0.12.0, or 0.12.1 can crash when trying to traverse certain malformed graphs due to an issue in the go-codec-dagpb dependency. Vulnerable nodes that work with these malformed graphs may crash leading to denial-of-service risks.
This particularly impacts nodes that download or export data that is controlled by external user input as there is the possibility that a malicious user of those services could (intentionally or unintentionally) cause the node to traverse a malformed graph. Some notable use cases include public gateways and pinning services which fetch data on behalf of users, as well as applications such as IPFS Companion which load data based on a user visiting a website with links to IPFS URLs.
### Patches
Versions v0.11.1 and v0.12.2 both resolve this issue. This should make it easy to upgrade, even if you have not yet performed the v0.12.0 migration.
For those running on forked versions of go-ipfs or who are on v0.10.0 and are having trouble with the v0.11.0 breaking changes, simply updating the version of `go-codec-dagpb` you are using to >=v1.3.2 should resolve the issue.
Any users of libraries within the go-ipfs ecosystem, even if not the go-ipfs package or binary itself, may be affected and should upgrade their dependency on go-codec-dagpb. You can check if your Go module has a dependency on `go-codec-dagpb` by running a command such as `go mod graph | grep go-codec-dagpb` in your module root.
### Workarounds
The best way to workaround this issue is to control exposure to any endpoints that allow for arbitrary IPLD traversals. This primarily includes the HTTP RPC API (https://docs.ipfs.io/reference/http/api ) and the Gateway API. If you are exposing those APIs, then do so within an environment where only trusted users and applications you control have access to it. You should be safe as long as your users and applications do not create malformed graphs, which should not happen using standard `go-ipfs` tooling.
If you previously had a more open access environment, then closing off access will only be sufficient if both of the following are true:
* The experimental GraphSync feature is disabled (https://github.com/ipfs/go-ipfs/blob/master/docs/experimental-features.md#graphsync)
* The only data being accessed is non-malformed data
### References
See also the [go-codec-dagpb security advisory](https://github.com/ipld/go-codec-dagpb/security/advisories/GHSA-g3vv-g2j5-45f2).
### For more information
If you have any questions or comments about this advisory:
* Ask in [IPFS Discord #ipfs-chatter](https://discord.gg/ipfs)
* Open an issue in [go-ipfs](https://github.com/ipld/go-ipfs)
| null |
2022-04-12T21:40:52Z
|
2022-04-08T22:09:23Z
|
HIGH
| 0
| null |
{'https://github.com/advisories/GHSA-mcq2-w56r-5w2w', 'https://github.com/ipfs/go-ipfs/security/advisories/GHSA-mcq2-w56r-5w2w'}
| null |
GHSA
|
GHSA-h74j-692g-48mq
|
Path Traversal in MHolt Archiver
|
All versions of archiver allow attacker to perform a Zip Slip attack via the "unarchive" functions. It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.
|
{'CVE-2019-10743'}
|
2021-05-18T15:31:53Z
|
2021-05-18T15:31:53Z
|
MODERATE
| 5.5
|
{'CWE-29'}
|
{'https://github.com/advisories/GHSA-h74j-692g-48mq', 'https://snyk.io/research/zip-slip-vulnerability', 'https://github.com/mholt/archiver/commit/8217ed3a206c0473b4ec1aff51375b398838073a', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMMHOLTARCHIVERCMDARC-174728,', 'https://github.com/snyk/zip-slip-vulnerability', 'https://github.com/mholt/archiver/pull/203', 'https://github.com/mholt/archiver/pull/169', 'https://nvd.nist.gov/vuln/detail/CVE-2019-10743'}
| null |
GHSA
|
GHSA-6h5q-96hp-9jgm
|
Moderate severity vulnerability that affects actionpack
|
Cross-site scripting (XSS) vulnerability in the number_to_currency helper in actionpack/lib/action_view/helpers/number_helper.rb in Ruby on Rails before 3.2.16 and 4.x before 4.0.2 allows remote attackers to inject arbitrary web script or HTML via the unit parameter.
|
{'CVE-2013-6415'}
|
2021-09-02T16:11:33Z
|
2017-10-24T18:33:36Z
|
MODERATE
| 0
|
{'CWE-79'}
|
{'http://rhn.redhat.com/errata/RHSA-2014-0008.html', 'http://secunia.com/advisories/56093', 'http://weblog.rubyonrails.org/2013/12/3/Rails_3_2_16_and_4_0_2_have_been_released/', 'https://nvd.nist.gov/vuln/detail/CVE-2013-6415', 'http://lists.opensuse.org/opensuse-updates/2013-12/msg00079.html', 'http://lists.opensuse.org/opensuse-updates/2014-01/msg00003.html', 'http://lists.opensuse.org/opensuse-updates/2013-12/msg00081.html', 'http://rhn.redhat.com/errata/RHSA-2013-1794.html', 'http://rhn.redhat.com/errata/RHSA-2014-1863.html', 'https://github.com/advisories/GHSA-6h5q-96hp-9jgm', 'http://www.securityfocus.com/bid/64077', 'https://groups.google.com/forum/message/raw?msg=ruby-security-ann/9WiRn2nhfq0/2K2KRB4LwCMJ', 'http://lists.opensuse.org/opensuse-updates/2013-12/msg00080.html', 'http://lists.opensuse.org/opensuse-updates/2014-01/msg00013.html', 'http://www.debian.org/security/2014/dsa-2888', 'http://lists.opensuse.org/opensuse-updates/2013-12/msg00082.html', 'https://puppet.com/security/cve/cve-2013-6415'}
| null |
GHSA
|
GHSA-fp63-499m-hq6m
|
Files or Directories Accessible to External Parties in ether/logs
|
### Impact
A vulnerability was found that allowed authenticated admin users to access any file on the server.
### Patches
The vulnerability has been fixed in 3.0.4.
### Workarounds
We recommend disabling the plugin if untrustworthy sources have admin access.
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [ether/logs](https://github.com/ethercreative/logs/issues)
|
{'CVE-2021-32752'}
|
2021-07-12T23:09:42Z
|
2021-07-12T16:53:00Z
|
HIGH
| 7.2
|
{'CWE-552'}
|
{'https://github.com/advisories/GHSA-fp63-499m-hq6m', 'https://github.com/ethercreative/logs/releases/tag/3.0.4', 'https://github.com/ethercreative/logs/commit/eb225cc78b1123a10ce2784790f232d71c2066c4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32752', 'https://github.com/ethercreative/logs/security/advisories/GHSA-fp63-499m-hq6m'}
| null |
GHSA
|
GHSA-mfg7-x5m7-6p8w
|
NULL Pointer Dereference in Google TensorFlow
|
NULL pointer dereference in Google TensorFlow before 1.12.2 could cause a denial of service via an invalid GIF file.
|
{'CVE-2019-9635'}
|
2021-08-03T21:26:24Z
|
2019-04-30T15:37:17Z
|
MODERATE
| 6.5
|
{'CWE-476'}
|
{'https://github.com/advisories/GHSA-mfg7-x5m7-6p8w', 'https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2019-001.md', 'https://nvd.nist.gov/vuln/detail/CVE-2019-9635'}
| null |
GHSA
|
GHSA-f8jj-45fj-44r6
|
Malicious Package in js-she3
|
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:13:40Z
|
2020-09-03T23:05:43Z
|
CRITICAL
| 9.8
|
{'CWE-506'}
|
{'https://github.com/advisories/GHSA-f8jj-45fj-44r6', 'https://www.npmjs.com/advisories/1287'}
| null |
GHSA
|
GHSA-9p9m-9xww-qjcx
|
Array size is not checked in sized-chunks
|
An issue was discovered in the sized-chunks crate through 0.6.2 for Rust. In the Chunk implementation, the array size is not checked when constructed with unit().
|
{'CVE-2020-25791'}
|
2021-08-25T20:45:06Z
|
2021-08-25T20:45:06Z
|
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-25791', 'https://github.com/advisories/GHSA-9p9m-9xww-qjcx'}
| null |
GHSA
|
GHSA-g98m-96g9-wfjq
|
Insecure path handling in Bundler
|
Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed.
|
{'CVE-2019-3881'}
|
2021-11-03T14:52:01Z
|
2021-05-10T14:53:59Z
|
HIGH
| 7
|
{'CWE-552', 'CWE-427'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-3881', 'https://github.com/rubygems/bundler/issues/6501', 'https://github.com/advisories/GHSA-g98m-96g9-wfjq', 'https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998', 'https://bugzilla.redhat.com/show_bug.cgi?id=1651826'}
| null |
GHSA
|
GHSA-3vjf-82ff-p4r3
|
Incorrect protocol extraction via \r, \n and \t characters
|
\r, \n and \t characters in user-input URLs can potentially lead to incorrect protocol extraction when using npm package urijs prior to version 1.19.11.
This can lead to XSS when the module is used to prevent passing in malicious javascript: links into HTML or Javascript (see following example):
````
const parse = require('urijs')
const express = require('express')
const app = express()
const port = 3000
input = "ja\r\nvascript:alert(1)"
url = parse(input)
console.log(url)
app.get('/', (req, res) => {
if (url.protocol !== "javascript:") {res.send("<iframe src=\'" + input + "\'>CLICK ME!</iframe>")}
})
app.listen(port, () => {
console.log(`Example app listening on port ${port}`)
})
````
|
{'CVE-2022-1243'}
|
2022-04-14T20:13:56Z
|
2022-04-06T00:01:31Z
|
HIGH
| 7.2
|
{'CWE-20'}
|
{'https://github.com/medialize/uri.js/commit/b0c9796aa1a95a85f40924fb18b1e5da3dc8ffae', 'https://nvd.nist.gov/vuln/detail/CVE-2022-1243', 'https://github.com/advisories/GHSA-3vjf-82ff-p4r3', 'https://huntr.dev/bounties/8c5afc47-1553-4eba-a98e-024e4cc3dfb7'}
| null |
GHSA
|
GHSA-m697-4v8f-55qg
|
Header dropping in traefik
|
# Impact
There exists a potential header vulnerability in Traefik's handling of the Connection header. Active exploitation of this issue is unlikely, as it requires that a removed header would lead to a privilege escalation, however, the Traefik team has addressed this issue to prevent any potential abuse.
# Details
If you have a chain of Traefik middlewares, and one of them sets a request header `Important-Security-Header`, then sending a request with the following Connection header will cause it to be removed before the request was sent:
```
curl 'https://example.com' -H "Connection: Important-Security-Header" -0
```
In this case, the backend does not see the request header `Important-Security-Header`.
# Patches
Traefik v2.4.x: https://github.com/traefik/traefik/releases/tag/v2.4.13
# Workarounds
No.
# For more information
If you have any questions or comments about this advisory, [open an issue](https://github.com/traefik/traefik/issues).
|
{'CVE-2021-32813'}
|
2021-08-31T20:57:11Z
|
2021-08-05T17:04:21Z
|
MODERATE
| 4.8
|
{'CWE-913'}
|
{'https://github.com/traefik/traefik/security/advisories/GHSA-m697-4v8f-55qg', 'https://github.com/traefik/traefik/pull/8319/commits/cbaf86a93014a969b8accf39301932c17d0d73f9', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32813', 'https://github.com/traefik/traefik/releases/tag/v2.4.13', 'https://github.com/advisories/GHSA-m697-4v8f-55qg'}
| null |
GHSA
|
GHSA-2877-693q-pj33
|
OS Command Injection in GenieACS
|
In GenieACS 1.2.x before 1.2.8, the UI interface API is vulnerable to unauthenticated OS command injection via the ping host argument (lib/ui/api.ts and lib/ping.ts). The vulnerability arises from insufficient input validation combined with a missing authorization check.
|
{'CVE-2021-46704'}
|
2022-03-14T21:30:23Z
|
2022-03-07T00:00:40Z
|
CRITICAL
| 9.8
|
{'CWE-78'}
|
{'https://github.com/genieacs/genieacs/commit/7f295beeecc1c1f14308a93c82413bb334045af6', 'https://github.com/genieacs/genieacs/releases/tag/v1.2.8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-46704', 'https://github.com/advisories/GHSA-2877-693q-pj33'}
| null |
GHSA
|
GHSA-j4f2-536g-r55m
|
Resource exhaustion in engine.io
|
Engine.IO before 4.0.0 allows attackers to cause a denial of service (resource consumption) via a POST request to the long polling transport.
|
{'CVE-2020-36048'}
|
2022-02-09T22:29:04Z
|
2022-02-09T22:29:04Z
|
HIGH
| 7.5
|
{'CWE-400'}
|
{'https://blog.caller.xyz/socketio-engineio-dos/', 'https://github.com/advisories/GHSA-j4f2-536g-r55m', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36048', 'https://github.com/bcaller/kill-engine-io', 'https://github.com/socketio/engine.io/commit/734f9d1268840722c41219e69eb58318e0b2ac6b'}
| null |
GHSA
|
GHSA-8gv6-g7vp-hr34
|
Hijacked Environment Variables in mysqljs
|
The `mysqljs` 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-16047'}
|
2021-01-14T15:33:11Z
|
2020-09-01T18:58:47Z
|
MODERATE
| 0
|
{'CWE-506'}
|
{'https://nodesecurity.io/advisories/494', 'https://www.npmjs.com/advisories/494', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16047', 'https://github.com/advisories/GHSA-8gv6-g7vp-hr34'}
| null |
GHSA
|
GHSA-88jf-7rch-32qc
|
Path Traversal in github.com/unknwon/cae/tz
|
"The ExtractTo function doesn't securely escape file paths in zip archives which include leading or non-leading "..". This allows an attacker to add or replace files system-wide."
|
{'CVE-2020-7668'}
|
2022-01-04T19:33:15Z
|
2021-05-18T20:31:18Z
|
HIGH
| 7.5
|
{'CWE-22'}
|
{'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAETZ-570384', 'https://nvd.nist.gov/vuln/detail/CVE-2020-7668', 'https://github.com/unknwon/cae/commit/07971c00a1bfd9dc171c3ad0bfab5b67c2287e11', 'https://github.com/advisories/GHSA-88jf-7rch-32qc'}
| null |
GHSA
|
GHSA-vr5m-3h59-7jcp
|
Prototype Pollution in think-helper
|
### Impact
The software receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
### Patches
`think-helper@1.1.3` patched it, anyone used `think-helper` should upgrade to `>=1.1.3` version.
### References
https://cwe.mitre.org/data/definitions/1321.html
### For more information
If you have any questions or comments about this advisory:
* Open an issue in [thinkjs/thinkjs](https://github.com/thinkjs/thinkjs)
* Email us at [i@imnerd.org](mailto:i@imnerd.org)
|
{'CVE-2021-32736'}
|
2022-04-19T19:03:01Z
|
2021-07-01T17:01:59Z
|
HIGH
| 7.5
|
{'CWE-1321', 'CWE-915'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-32736', 'https://github.com/advisories/GHSA-vr5m-3h59-7jcp', 'https://github.com/thinkjs/think-helper/security/advisories/GHSA-vr5m-3h59-7jcp'}
| null |
GHSA
|
GHSA-p2rp-cmjq-r7wm
|
Shell command injection in Apache Syncope
|
In Apache Syncope 2.1.X releases prior to 2.1.7, when the Flowable extension is enabled, an administrator with workflow entitlements can use Shell Service Tasks to perform malicious operations, including but not limited to file read, file write, and code execution.
|
{'CVE-2020-11977'}
|
2021-06-16T17:19:12Z
|
2021-06-16T17:19:12Z
|
HIGH
| 7.2
|
{'CWE-78'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2020-11977', 'https://syncope.apache.org/security#CVE-2020-11977:_Remote_Code_Execution_via_Flowable_workflow_definition', 'https://github.com/advisories/GHSA-p2rp-cmjq-r7wm'}
| null |
GHSA
|
GHSA-35qp-xq9f-2rjx
|
Improper Privilege Management in HashiCorp Nomad
|
HashiCorp Nomad and Nomad Enterprise up to 0.12.9 exec and java task drivers can access processes associated with other tasks on the same node. Fixed in 0.12.10, and 1.0.3.
|
{'CVE-2021-3283'}
|
2021-06-24T20:28:28Z
|
2021-06-24T20:28:28Z
|
HIGH
| 7.5
|
{'CWE-269'}
|
{'https://discuss.hashicorp.com/t/hcsec-2021-01-nomad-s-exec-and-java-task-drivers-did-not-isolate-processes/20332', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3283', 'https://github.com/advisories/GHSA-35qp-xq9f-2rjx'}
| null |
GHSA
|
GHSA-jc8g-xhw5-6x46
|
Moderate severity vulnerability that affects Microsoft.NETCore.UniversalWindowsPlatform and Microsoft.NETCore.UniversalWindowsPlatform
|
Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka ".NET Security Feature Bypass Vulnerability."
|
{'CVE-2018-0786'}
|
2021-12-03T14:54:43Z
|
2018-10-16T19:59:05Z
|
MODERATE
| 0
| null |
{'https://github.com/advisories/GHSA-jc8g-xhw5-6x46'}
| null |
GHSA
|
GHSA-c45w-2wxr-pp53
|
Heap OOB read in `tf.raw_ops.Dequantize`
|
### Impact
Due to lack of validation in `tf.raw_ops.Dequantize`, an attacker can trigger a read from outside of bounds of heap allocated data:
```python
import tensorflow as tf
input_tensor=tf.constant(
[75, 75, 75, 75, -6, -9, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\
-10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\
-10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10, -10,\
-10, -10, -10, -10], shape=[5, 10], dtype=tf.int32)
input_tensor=tf.cast(input_tensor, dtype=tf.quint8)
min_range = tf.constant([-10], shape=[1], dtype=tf.float32)
max_range = tf.constant([24, 758, 758, 758, 758], shape=[5], dtype=tf.float32)
tf.raw_ops.Dequantize(
input=input_tensor, min_range=min_range, max_range=max_range, mode='SCALED',
narrow_range=True, axis=0, dtype=tf.dtypes.float32)
```
The [implementation](https://github.com/tensorflow/tensorflow/blob/26003593aa94b1742f34dc22ce88a1e17776a67d/tensorflow/core/kernels/dequantize_op.cc#L106-L131) accesses the `min_range` and `max_range` tensors in parallel but fails to check that they have the same shape:
```cc
if (num_slices == 1) {
const float min_range = input_min_tensor.flat<float>()(0);
const float max_range = input_max_tensor.flat<float>()(0);
DequantizeTensor(ctx, input, min_range, max_range, &float_output);
} else {
...
auto min_ranges = input_min_tensor.vec<float>();
auto max_ranges = input_max_tensor.vec<float>();
for (int i = 0; i < num_slices; ++i) {
DequantizeSlice(ctx->eigen_device<Device>(), ctx,
input_tensor.template chip<1>(i), min_ranges(i),
max_ranges(i), output_tensor.template chip<1>(i));
...
}
}
```
### Patches
We have patched the issue in GitHub commit [5899741d0421391ca878da47907b1452f06aaf1b](https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b).
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-29582'}
|
2021-05-21T14:26:32Z
|
2021-05-21T14:26:32Z
|
LOW
| 2.5
|
{'CWE-125'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2021-29582', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c45w-2wxr-pp53', 'https://github.com/tensorflow/tensorflow/commit/5899741d0421391ca878da47907b1452f06aaf1b', 'https://github.com/advisories/GHSA-c45w-2wxr-pp53'}
| null |
GHSA
|
GHSA-ccw8-7688-vqx4
|
Privilege Escalation in HashiCorp Consul
|
HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to access server-only functionality, enabling privilege escalation. Fixed in 1.8.15, 1.9.9 and 1.10.2.
|
{'CVE-2021-37219'}
|
2021-09-14T18:47:10Z
|
2021-09-08T20:14:48Z
|
HIGH
| 8.8
|
{'CWE-295'}
|
{'https://discuss.hashicorp.com/t/hcsec-2021-22-consul-raft-rpc-privilege-escalation/29024', 'https://www.hashicorp.com/blog/category/consul', 'https://github.com/advisories/GHSA-ccw8-7688-vqx4', 'https://nvd.nist.gov/vuln/detail/CVE-2021-37219'}
| null |
GHSA
|
GHSA-w4vg-rf63-f3j3
|
Arbitrary code using "crafted image file" approach affecting Pillow
|
Pillow before 3.3.2 allows context-dependent attackers to execute arbitrary code by using the "crafted image file" approach, related to an "Insecure Sign Extension" issue affecting the ImagingNew in Storage.c component.
|
{'CVE-2016-9190'}
|
2022-04-26T18:06:20Z
|
2018-07-12T14:45:42Z
|
HIGH
| 7.8
|
{'CWE-284'}
|
{'https://github.com/python-pillow/Pillow/issues/2105', 'https://nvd.nist.gov/vuln/detail/CVE-2016-9190', 'http://pillow.readthedocs.io/en/3.4.x/releasenotes/3.3.2.html', 'https://github.com/advisories/GHSA-w4vg-rf63-f3j3', 'http://www.securityfocus.com/bid/94234', 'http://www.debian.org/security/2016/dsa-3710', 'https://github.com/python-pillow/Pillow/pull/2146/commits/5d8a0be45aad78c5a22c8d099118ee26ef8144af', 'https://security.gentoo.org/glsa/201612-52'}
| null |
GHSA
|
GHSA-992f-wf4w-x36v
|
Prototype Pollution in merge-objects
|
All versions of `merge-objects` are vulnerable to Prototype Pollution.
## Recommendation
No fix is available for this vulnerability at this time. It is our recommendation to use an alternative package.
| null |
2021-09-24T20:46:34Z
|
2020-09-01T21:16:13Z
|
LOW
| 0
|
{'CWE-1321'}
|
{'https://hackerone.com/reports/310706', 'https://github.com/advisories/GHSA-992f-wf4w-x36v', 'https://www.npmjs.com/advisories/716'}
| null |
GHSA
|
GHSA-vv52-3mrp-455m
|
Malicious Package in m-backdoor
|
All versions of `m-backdoor` contain malicious code. The package downloads a file from a remote server and executes it as a preinstall script. At the time of the release of this advisory the downloaded file only defaces websites by removing elements randomly from the DOM.
## Recommendation
Remove the package from your system.
| null |
2021-10-04T21:10:35Z
|
2020-09-03T15:53:36Z
|
CRITICAL
| 0
|
{'CWE-506'}
|
{'https://www.npmjs.com/advisories/1513', 'https://github.com/advisories/GHSA-vv52-3mrp-455m'}
| null |
GHSA
|
GHSA-5vfx-8w6m-h3v4
|
Authentication bypass due to improper user-provided security token verification
|
A malicious user can modify the contents of a `confirmation_token` input during the two-factor authentication process to reference a cache value not associated with the login attempt. In rare cases this can allow a malicious actor to authenticate as a random user in the Panel. The malicious user must target an account with two-factor authentication enabled, and then must provide a correct two-factor authentication token before being authenticated as that user.
## Impact
Due to a validation flaw in the logic handling user authentication during the two-factor authentication process a malicious user can trick the system into loading credentials for an arbitrary user by modifying the token sent to the server. This authentication flaw is present in the `LoginCheckpointController@__invoke` method which handles two-factor authentication for a user.
This controller looks for a request input parameter called `confirmation_token` which is expected to be a 64 character random alpha-numeric string that references a value within the Panel's cache containing a `user_id` value. This value is then used to fetch the user that attempted to login, and lookup their two-factor authentication token. Due to the design of this system, any element in the cache that contains only digits could be referenced by a malicious user, and whatever value is stored at that position would be used as the `user_id`.
There are a few different areas of the Panel that store values into the cache that are integers, and a user who determines what those cache keys are could pass one of those keys which would cause this code pathway to reference an arbitrary user.
## Scope
At its heart this is a high-risk login bypass vulnerability. However, there are a few additional conditions that must be met in order for this to be successfully executed, notably:
1.) The account referenced by the malicious cache key **must** have two-factor authentication enabled. An account without two-factor authentication would cause an exception to be triggered by the authentication logic, thusly exiting this authentication flow.
2.) Even if the malicious user is able to reference a valid cache key that references a valid user account with two-factor authentication, they **must** provide a valid two-factor authentication token.
However, due to the design of this endpoint once a valid user account is found with two-factor authentication enabled there is no rate-limiting present, thusly allowing an attacker to brute force combinations until successful. This leads to a third condition that must be met:
3.) For the duration of this attack sequence the cache key being referenced must continue to exist with a valid `user_id` value. Depending on the specific key being used for this attack, this value may disappear quickly, or be changed by other random user interactions on the Panel, outside the control of the attacker.
### About the Severity
As you may have noticed, this is not a trivial authentication bypass bug to exploit, and is likely incredibly difficult for a layperson to pull off. However, the severity of this disclosure has been prepared based on the nature of the bug and the potential for unexpected administrative account access under very rare conditions.
## Mitigation
In order to mitigate this vulnerability the underlying authentication logic was changed to use an encrypted session store that the user is therefore unable to control the value of. This completely removed the use of a user-controlled value being used. In addition, the code was audited to ensure this type of vulnerability is not present elsewhere.
If you have any questions or concerns about the content of this disclosure please contact `Tactical Fish#8008` on Discord, or email `dane ät pterodactyl.io`.
|
{'CVE-2021-41129'}
|
2021-10-12T21:45:12Z
|
2021-10-04T20:14:13Z
|
HIGH
| 8.1
|
{'CWE-502', 'CWE-639', 'CWE-807'}
|
{'https://github.com/pterodactyl/panel/security/advisories/GHSA-5vfx-8w6m-h3v4', 'https://github.com/advisories/GHSA-5vfx-8w6m-h3v4', 'https://github.com/pterodactyl/panel/blob/v1.6.2/CHANGELOG.md#v162', 'https://github.com/pterodactyl/panel/commit/4a84c36009be10dbd83051ac1771662c056e4977', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41129', 'https://github.com/pterodactyl/panel/releases/tag/v1.6.2'}
| null |
GHSA
|
GHSA-9vp5-m38w-j776
|
Aliases are never checked in helm
|
### Impact
During a security audit of Helm's code base, security researchers at Trail of Bits identified a bug in which the `alias` field on a `Chart.yaml` is not properly sanitized. This could lead to the injection of unwanted information into a chart.
### Patches
This issue has been patched in Helm 3.3.2 and 2.16.11
### Workarounds
Manually review the `dependencies` field of any untrusted chart, verifying that the `alias` field is either not used, or (if used) does not contain newlines or path characters.
|
{'CVE-2020-15184'}
|
2021-11-19T15:29:13Z
|
2021-05-24T16:56:58Z
|
LOW
| 3.7
|
{'CWE-74', 'CWE-20'}
|
{'https://github.com/helm/helm/commit/e7c281564d8306e1dcf8023d97f972449ad74850', 'https://github.com/helm/helm/commit/6aab63765f99050b115f0aec3d6350c85e8da946', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15184', 'https://github.com/helm/helm/security/advisories/GHSA-9vp5-m38w-j776', 'https://github.com/advisories/GHSA-9vp5-m38w-j776'}
| null |
GHSA
|
GHSA-vgmw-9cww-qq99
|
Incorrect Authorization in calibreweb
|
calibreweb prior to version 0.6.16 contains an Incorrect Authorization vulnerability.
|
{'CVE-2022-0273'}
|
2022-02-16T22:04:14Z
|
2022-01-31T00:00:29Z
|
MODERATE
| 6.5
|
{'CWE-863', 'CWE-284'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-0273', 'https://huntr.dev/bounties/8f27686f-d698-4ab6-8ef0-899125792f13', 'https://github.com/janeczku/calibre-web/commit/0c0313f375bed7b035c8c0482bbb09599e16bfcf', 'https://github.com/advisories/GHSA-vgmw-9cww-qq99'}
| null |
GHSA
|
GHSA-54xj-q58h-9x57
|
Arbitrary File Write in iobroker.admin
|
Versions of `iobroker.admin` prior to 3.6.12 are vulnerable to Path Traversal. The package fails to restrict access to folders outside of the intended folder in the `/log/` route, which may allow attackers to include arbitrary files in the system. An attacker would need to be authenticated to perform the attack but the package has authentication disabled by default.
## Recommendation
Upgrade to version 3.6.12 or later.
|
{'CVE-2019-10765'}
|
2021-10-01T20:14:11Z
|
2020-09-04T15:24:56Z
|
CRITICAL
| 9.8
|
{'CWE-22'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2019-10765', 'https://github.com/ioBroker/ioBroker.admin/commit/16b2b325ab47896090bc7f54b77b0a97ed74f5cd', 'https://github.com/advisories/GHSA-54xj-q58h-9x57', 'https://www.npmjs.com/advisories/1346', 'https://snyk.io/vuln/SNYK-JS-IOBROKERADMIN-534634'}
| null |
GHSA
|
GHSA-3382-r9q8-4hfg
|
Allocation of Resources Without Limits or Throttling in github.com/hashicorp/nomad
|
HashiCorp Nomad and Nomad Enterprise 1.x before 1.0.17, 1.1.x before 1.1.12, and 1.2.x before 1.2.6 is vulnerable to Allocation of Resources Without Limits or Throttling.
|
{'CVE-2022-24685'}
|
2022-04-01T20:11:34Z
|
2022-03-01T00:00:28Z
|
HIGH
| 7.5
|
{'CWE-770'}
|
{'https://security.netapp.com/advisory/ntap-20220331-0007/', 'https://discuss.hashicorp.com/t/hcsec-2022-03-nomad-malformed-job-parsing-results-in-excessive-cpu-usage/35561', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24685', 'https://github.com/advisories/GHSA-3382-r9q8-4hfg', 'https://discuss.hashicorp.com'}
| null |
GHSA
|
GHSA-rw2c-c256-3r53
|
Data races in hashconsing
|
An issue was discovered in the hashconsing crate before 1.1.0 for Rust. Because HConsed does not have bounds on its Send trait or Sync trait, memory corruption can occur.
|
{'CVE-2020-36215'}
|
2021-08-25T20:51:52Z
|
2021-08-25T20:51:52Z
|
HIGH
| 7.5
|
{'CWE-662', 'CWE-787'}
|
{'https://github.com/AdrienChampion/hashconsing/issues/1', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36215', 'https://rustsec.org/advisories/RUSTSEC-2020-0107.html', 'https://github.com/advisories/GHSA-rw2c-c256-3r53'}
| null |
GHSA
|
GHSA-x7wf-5mjc-6x76
|
SSRF attacks via tracebacks in Plone
|
Plone before 5.2.3 allows SSRF attacks via the tracebacks feature (only available to the Manager role).
|
{'CVE-2020-28735'}
|
2021-04-07T21:13:44Z
|
2021-04-07T21:13:44Z
|
HIGH
| 8.8
|
{'CWE-918'}
|
{'https://github.com/advisories/GHSA-x7wf-5mjc-6x76', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28735', 'https://github.com/plone/Products.CMFPlone/issues/3209', 'https://dist.plone.org/release/5.2.3/RELEASE-NOTES.txt', 'https://www.misakikata.com/codes/plone/python-en.html'}
| null |
GHSA
|
GHSA-3wjm-33mw-h388
|
Malicious Package in s3asy
|
Version 0.4.8 of `s3asy` 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
If version 0.4.8 of this module is found installed you will want to replace it with a version before or after 0.4.8. In addition to replacing the installed module, you will also want to evaluate your application to determine whether or not user data was compromised.
| null |
2020-09-01T20:34:14Z
|
2020-09-01T20:34:14Z
|
CRITICAL
| 0
| null |
{'https://github.com/advisories/GHSA-3wjm-33mw-h388', 'https://www.npmjs.com/advisories/636'}
| null |
GHSA
|
GHSA-3gx7-xhv7-5mx3
|
Arbitrary Code Execution in eslint-utils
|
Versions of `eslint-utils` >=1.2.0 or <1.4.1 are vulnerable to Arbitrary Code Execution. The `getStaticValue` does not properly sanitize user input allowing attackers to supply malicious input that executes arbitrary code during the linting process. The `getStringIfConstant` and `getPropertyName` functions are not affected.
## Recommendation
Upgrade to version 1.4.1 or later.
|
{'CVE-2019-15657'}
|
2021-08-31T21:04:33Z
|
2019-08-26T16:59:56Z
|
CRITICAL
| 9.8
|
{'CWE-20'}
|
{'https://github.com/advisories/GHSA-3gx7-xhv7-5mx3', 'https://nvd.nist.gov/vuln/detail/CVE-2019-15657', 'https://www.npmjs.com/advisories/1118', 'https://eslint.org/blog/2019/08/eslint-v6.2.1-released', 'https://github.com/mysticatea/eslint-utils/security/advisories/GHSA-3gx7-xhv7-5mx3'}
| null |
GHSA
|
GHSA-3qgw-p4fm-x7gf
|
Division by zero in TFLite's convolution code
|
### Impact
TFLite's [convolution code](https://github.com/tensorflow/tensorflow/blob/09c73bca7d648e961dd05898292d91a8322a9d45/tensorflow/lite/kernels/conv.cc) has multiple division where the divisor is controlled by the user and not checked to be non-zero. For example:
```cc
const int input_size = NumElements(input) / SizeOfDimension(input, 0);
```
### Patches
We have patched the issue in GitHub commit [ff489d95a9006be080ad14feb378f2b4dac35552](https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552).
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-29594'}
|
2021-05-21T14:27:45Z
|
2021-05-21T14:27:45Z
|
LOW
| 2.5
|
{'CWE-369'}
|
{'https://github.com/tensorflow/tensorflow/commit/ff489d95a9006be080ad14feb378f2b4dac35552', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29594', 'https://github.com/advisories/GHSA-3qgw-p4fm-x7gf', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-3qgw-p4fm-x7gf'}
| null |
GHSA
|
GHSA-gq28-h5vg-8prx
|
Privilege escalation in spring security
|
Spring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.
|
{'CVE-2021-22112'}
|
2021-10-21T18:14:50Z
|
2021-05-10T15:22:39Z
|
HIGH
| 8.8
|
{'CWE-269'}
|
{'https://lists.apache.org/thread.html/ra6389b1b82108a3b6bbcd22979f7665fd437c2a3408c9509a15a9ca1@%3Cpluto-dev.portals.apache.org%3E', 'https://lists.apache.org/thread.html/r89aa1b48a827f5641310305214547f1d6b2101971a49b624737c497f@%3Cpluto-dev.portals.apache.org%3E', 'https://www.jenkins.io/security/advisory/2021-02-19/', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://lists.apache.org/thread.html/r163b3e4e39803882f5be05ee8606b2b9812920e196daa2a82997ce14@%3Cpluto-dev.portals.apache.org%3E', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22112', 'https://lists.apache.org/thread.html/r2cb05e499807900ba23e539643eead9c5f0652fd271f223f89da1804@%3Cpluto-scm.portals.apache.org%3E', 'https://lists.apache.org/thread.html/r37423ec7eea340e92a409452c35b649dce02fdc467f0b3f52086c177@%3Cpluto-dev.portals.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/spring-projects/spring-security/releases/tag/5.4.4', 'https://github.com/advisories/GHSA-gq28-h5vg-8prx', 'https://lists.apache.org/thread.html/r413e380088c427f56102968df89ef2f336473e1b56b7d4b3a571a378@%3Cpluto-dev.portals.apache.org%3E', 'https://lists.apache.org/thread.html/ra53677224fe4f04c2599abc88032076faa18dc84b329cdeba85d4cfc@%3Cpluto-scm.portals.apache.org%3E', 'http://www.openwall.com/lists/oss-security/2021/02/19/7', 'https://tanzu.vmware.com/security/cve-2021-22112', 'https://lists.apache.org/thread.html/r3868207b967f926819fe3aa8d33f1666429be589bb4a62104a49f4e3@%3Cpluto-dev.portals.apache.org%3E', 'https://lists.apache.org/thread.html/r390783b3b1c59b978131ac08390bf77fbb3863270cbde59d5b0f5fde@%3Cpluto-dev.portals.apache.org%3E', 'https://lists.apache.org/thread.html/redbd004a503b3520ae5746c2ab5e93fd7da807a8c128e60d2002cd9b@%3Cissues.nifi.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html'}
| null |
GHSA
|
GHSA-53m6-44rc-h2q5
|
Missing server signature validation in OctoberCMS
|
### Impact
This advisory affects authors of plugins and themes listed on the October CMS marketplace where an end-user will inadvertently expose authors to potential financial loss by entering their private license key into a compromised server.
It has been disclosed that a project fork of October CMS v1.0 is using a compromised gateway to access the October CMS marketplace service. The compromised gateway captures the personal/business information of users and authors, including private source code files. It was also disclosed that captured plugin files are freely redistributed to other users without authorization.
1. End-users are provided with a forked version of October CMS v1.0. The provided software is modified to use a compromised gateway server.
2. The user is instructed to enter their October CMS license key into the administration panel to access the October CMS marketplace. The key is sent to the compromised server while appearing to access the genuine October CMS gateway server.
3. The compromised gateway server uses a "man in the middle" mechanism that captures information while forwarding the request to the genuine October CMS gateway and relaying the response back to the client.
4. The compromised gateway server stores the license key and other information about the user account including client name, email address and contents of purchased plugins and privately uploaded plugin files.
5. The stored plugin files are made available to other users of the compromised gateway server.
### Patches
The issue has been patched in Build 475 (v1.0.475) and v1.1.11.
### Workarounds
Apply https://github.com/octobercms/october/commit/e3b455ad587282f0fbcb7763c6d9c3d000ca1e6a to your installation manually if unable to upgrade to Build 475 or v1.1.11.
### Recommendations
We recommend the following steps to make sure your account information stays secure:
- Do not share your license key with anyone except October CMS.
- Check to make sure that your gateway update server has not been modified.
- Be aware of phishing websites, including other platforms that use the same appearance.
- For authors, you may contact us for help requesting the removal of affected plugins.
- Before providing plugin support, verify that the user holds a legitimate copy of the plugin.
### References
Credits for research on this exploit:
• Nikita Khaetsky
### For more information
If you have any questions or comments about this advisory:
* Email us at [hello@octobercms.com](mailto:hello@octobercms.com)
|
{'CVE-2022-23655'}
|
2022-03-08T18:23:38Z
|
2022-02-24T13:09:30Z
|
MODERATE
| 4.8
|
{'CWE-347'}
|
{'https://nvd.nist.gov/vuln/detail/CVE-2022-23655', 'https://github.com/octobercms/october/commit/e3b455ad587282f0fbcb7763c6d9c3d000ca1e6a', 'https://github.com/advisories/GHSA-53m6-44rc-h2q5', 'https://github.com/octobercms/october/security/advisories/GHSA-53m6-44rc-h2q5'}
| null |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.