ecosystem
stringclasses
11 values
vuln_id
stringlengths
10
19
summary
stringlengths
4
220
details
stringlengths
34
13.5k
aliases
stringlengths
17
87
modified_date
stringdate
2019-03-26 14:13:00
2022-05-10 08:46:52
published_date
stringdate
2012-06-17 03:41:00
2022-05-10 08:46:50
severity
stringclasses
5 values
score
float64
0
10
cwe_id
stringclasses
581 values
refs
stringlengths
82
11.6k
introduced
stringclasses
843 values
code_refs
stringlengths
46
940
commits
stringlengths
46
940
GHSA
GHSA-c2q3-4qrh-fm48
Deserialization of untrusted data in Jackson Databind
FasterXML jackson-databind 2.x before 2.9.10.5 mishandles the interaction between serialization gadgets and typing, related to oracle.jms.AQjmsQueueConnectionFactory, oracle.jms.AQjmsXATopicConnectionFactory, oracle.jms.AQjmsTopicConnectionFactory, oracle.jms.AQjmsXAQueueConnectionFactory, and oracle.jms.AQjmsXAConnectionFactory (aka weblogic/oracle-aqjms).
{'CVE-2020-14061'}
2021-10-21T21:08:31Z
2020-06-18T14:44:50Z
HIGH
8.1
{'CWE-502'}
{'https://snyk.io/vuln/SNYK-JAVA-COMFASTERXMLJACKSONCORE-572316', 'https://medium.com/@cowtowncoder/on-jackson-cves-dont-panic-here-is-what-you-need-to-know-54cd0d6e8062', 'https://security.netapp.com/advisory/ntap-20200702-0003/', 'https://lists.debian.org/debian-lts-announce/2020/07/msg00001.html', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/FasterXML/jackson-databind/issues/2698', 'https://github.com/FasterXML/jackson-databind/commit/5c8642aeae9c756b438ab7637c90ef3c77966e6e', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://github.com/advisories/GHSA-c2q3-4qrh-fm48', 'https://nvd.nist.gov/vuln/detail/CVE-2020-14061'}
null
{'https://github.com/FasterXML/jackson-databind/commit/5c8642aeae9c756b438ab7637c90ef3c77966e6e'}
{'https://github.com/FasterXML/jackson-databind/commit/5c8642aeae9c756b438ab7637c90ef3c77966e6e'}
GHSA
GHSA-6gr8-c3m5-mvrg
Exposure of Sensitive Information to an Unauthorized Actor
Shopware is an open source eCommerce platform. In versions prior to 6.4.1.1 private files publicly accessible with Cloud Storage providers when the hashed URL is known. Users are recommend to first change their configuration to set the correct visibility according to the documentation. The visibility must be at the same level as `type`. When the Storage is saved on Amazon AWS we recommending disabling public access to the bucket containing the private files: https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-control-block-public-access.html. Otherwise, update to Shopware 6.4.1.1 or install or update the Security plugin (https://store.shopware.com/en/detail/index/sArticle/518463/number/Swag136939272659) and run the command `./bin/console s3:set-visibility` to correct your cloud file visibilities.
{'CVE-2021-32717'}
2021-09-08T18:00:47Z
2021-09-08T18:00:47Z
HIGH
7.5
{'CWE-200'}
{'https://github.com/shopware/platform/commit/ba52f683372b8417a00e9014f481ed3d539f34b3', 'https://github.com/shopware/platform/security/advisories/GHSA-vrf2-xghr-j52v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-32717', 'https://docs.shopware.com/en/shopware-6-en/security-updates/security-update-06-2021', 'https://github.com/advisories/GHSA-6gr8-c3m5-mvrg'}
null
{'https://github.com/shopware/platform/commit/ba52f683372b8417a00e9014f481ed3d539f34b3'}
{'https://github.com/shopware/platform/commit/ba52f683372b8417a00e9014f481ed3d539f34b3'}
GHSA
GHSA-6r92-cgxc-r5fg
Denial of service in CBOR library
### Impact Due to this library's use of an inefficient algorithm, it is vulnerable to a denial of service attack when a maliciously crafted input is passed to `DecodeFromBytes` or other CBOR decoding mechanisms in this library. Affected versions _include_ versions 4.0.0 through 4.5.0. This vulnerability was privately reported to me. ### Patches This issue has been fixed in version 4.5.1. Users should use the latest version of this library. (The latest version is not necessarily 4.5.1. Check the [NuGet page](https://www.nuget.org/packages/PeterO.Cbor) to see the latest version's version number.) ### Workarounds Again, users should use the latest version of this library. In the meantime, note that the inputs affected by this issue are all CBOR maps or contain CBOR maps. An input that decodes to a single CBOR object is not capable of containing a CBOR map if— - it begins with a byte other than 0x80 through 0xDF, or - it does not contain a byte in the range 0xa0 through 0xBF. Such an input is not affected by this vulnerability and an application can choose to perform this check before passing it to a CBOR decoding mechanism. ### For more information If you have any questions or comments about this advisory: * Open an issue in [the CBOR repository](https://github.com/peteroupc/CBOR).
null
2022-01-24T22:05:32Z
2022-01-21T23:35:35Z
HIGH
0
{'CWE-407'}
{'https://github.com/peteroupc/CBOR/security/advisories/GHSA-6r92-cgxc-r5fg', 'https://github.com/advisories/GHSA-6r92-cgxc-r5fg', 'https://github.com/peteroupc/CBOR/commit/b4117dbbb4cd5a4a963f9d0c9aa132f033e15b95', 'https://github.com/peteroupc/CBOR/compare/v4.5...v4.5.1'}
null
{'https://github.com/peteroupc/CBOR/commit/b4117dbbb4cd5a4a963f9d0c9aa132f033e15b95'}
{'https://github.com/peteroupc/CBOR/commit/b4117dbbb4cd5a4a963f9d0c9aa132f033e15b95'}
GHSA
GHSA-rjf2-j2r6-q8gr
Prototype Pollution in vm2
This affects the package vm2 before 3.9.4. Prototype Pollution attack vector can lead to sandbox escape and execution of arbitrary code on the host machine.
{'CVE-2021-23449'}
2021-11-01T14:07:45Z
2021-10-19T15:28:45Z
CRITICAL
9.8
{'CWE-1321', 'CWE-915'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-23449', 'https://github.com/patriksimek/vm2/releases/tag/3.9.4', 'https://snyk.io/vuln/SNYK-JS-VM2-1585918', 'https://github.com/patriksimek/vm2/issues/363', 'https://github.com/patriksimek/vm2/commit/b4f6e2bd2c4a1ef52fc4483d8e35f28bc4481886', 'https://security.netapp.com/advisory/ntap-20211029-0010/', 'https://github.com/advisories/GHSA-rjf2-j2r6-q8gr'}
null
{'https://github.com/patriksimek/vm2/commit/b4f6e2bd2c4a1ef52fc4483d8e35f28bc4481886'}
{'https://github.com/patriksimek/vm2/commit/b4f6e2bd2c4a1ef52fc4483d8e35f28bc4481886'}
GHSA
GHSA-82hx-w2r5-c2wq
Allocation of Resources Without Limits or Throttling and Uncontrolled Memory Allocation in Kubernetes
The Kubernetes API server component in versions prior to 1.15.9, 1.16.0-1.16.6, and 1.17.0-1.17.2 has been found to be vulnerable to a denial of service attack via successful API requests.
{'CVE-2020-8552'}
2022-04-12T22:00:04Z
2022-02-15T01:57:18Z
MODERATE
5.3
{'CWE-789', 'CWE-400'}
{'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3SOCLOPTSYABTE4CLTSPDIFE6ZZZR4LX/', 'https://security.netapp.com/advisory/ntap-20200413-0003/', 'https://github.com/advisories/GHSA-82hx-w2r5-c2wq', 'https://github.com/kubernetes/kubernetes/commit/5978856c4c7f10737a11c9540fe60b8475beecbb', 'https://github.com/kubernetes/kubernetes/issues/89378', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8552', 'https://github.com/kubernetes/kubernetes/pull/87669', 'https://groups.google.com/forum/#!topic/kubernetes-security-announce/2UOlsba2g0s'}
null
{'https://github.com/kubernetes/kubernetes/commit/5978856c4c7f10737a11c9540fe60b8475beecbb'}
{'https://github.com/kubernetes/kubernetes/commit/5978856c4c7f10737a11c9540fe60b8475beecbb'}
GHSA
GHSA-fqh4-rh59-xhvf
Denial of service
The package `github.com/pires/go-proxyproto` before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in the code, a deliberately malformed V1 header could be used to exhaust memory in a server process using this code - and create a DoS. This can be exploited by sending a stream starting with PROXY and continuing to send data (which does not contain a newline) until the target stops acknowledging. The risk here is small, because only trusted sources should be allowed to send proxy protocol headers.
{'CVE-2021-23351'}
2021-05-18T21:07:43Z
2021-05-18T21:07:43Z
MODERATE
4.9
{'CWE-400'}
{'https://github.com/pires/go-proxyproto/commit/7f48261db810703d173f27f3309a808cc2b49b8b', 'https://github.com/pires/go-proxyproto/pull/71', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C36IBVOZXRTWM7MGTRUTOM56P5RR74VU/', 'https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMPIRESGOPROXYPROTO-1081577', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4BNVGJMVI3ZTZ675EFPUHPGXCKCGSX46/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23351', 'https://github.com/pires/go-proxyproto/issues/69', 'https://github.com/advisories/GHSA-fqh4-rh59-xhvf'}
null
{'https://github.com/pires/go-proxyproto/commit/7f48261db810703d173f27f3309a808cc2b49b8b'}
{'https://github.com/pires/go-proxyproto/commit/7f48261db810703d173f27f3309a808cc2b49b8b'}
GHSA
GHSA-79jw-2f46-wv22
Authenticated remote code execution in October CMS
### Impact An authenticated user with the permissions to create, modify and delete website pages can exploit this vulnerability to bypass `cms.safe_mode` / `cms.enableSafeMode` in order to execute arbitrary code. - This issue only affects admin panels that rely on safe mode and restricted permissions. - To exploit this vulnerability, an attacker must first have access to the backend area. ### Patches The issue has been patched in Build 474 (v1.0.474) and v1.1.10. ### Workarounds Apply https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe to your installation manually if unable to upgrade to Build 474 or v1.1.10. ### References Credits to: - David Miller ### 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-21705'}
2022-04-19T19:03:20Z
2022-02-23T21:08:44Z
HIGH
7.2
{'CWE-74'}
{'https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe', 'https://github.com/octobercms/october/security/advisories/GHSA-79jw-2f46-wv22', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21705', 'https://github.com/advisories/GHSA-79jw-2f46-wv22'}
null
{'https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe'}
{'https://github.com/octobercms/library/commit/c393c5ce9ca2c5acc3ed6c9bb0dab5ffd61965fe'}
GHSA
GHSA-j7c4-2xj8-wm7r
Moderate severity vulnerability that affects kdcproxy
python-kdcproxy before 0.3.2 allows remote attackers to cause a denial of service via a large POST request.
{'CVE-2015-5159'}
2021-09-14T19:12:11Z
2018-11-01T14:49:30Z
HIGH
7.5
{'CWE-20'}
{'https://nvd.nist.gov/vuln/detail/CVE-2015-5159', 'https://github.com/latchset/kdcproxy/commit/f274aa6787cb8b3ec1cc12c440a56665b7231882', 'https://github.com/advisories/GHSA-j7c4-2xj8-wm7r', 'https://bugzilla.redhat.com/show_bug.cgi?id=1245200'}
null
{'https://github.com/latchset/kdcproxy/commit/f274aa6787cb8b3ec1cc12c440a56665b7231882'}
{'https://github.com/latchset/kdcproxy/commit/f274aa6787cb8b3ec1cc12c440a56665b7231882'}
GHSA
GHSA-gcr6-rf47-jrgf
Loaded Databook of Tablib prone to python insertion resulting in command execution
An exploitable vulnerability exists in the Databook loading functionality of Tablib 0.11.4. A yaml loaded Databook can execute arbitrary python commands resulting in command execution. An attacker can insert python into loaded yaml to trigger this vulnerability.
{'CVE-2017-2810'}
2022-04-26T18:16:34Z
2018-07-13T16:01:25Z
CRITICAL
9.8
null
{'https://github.com/jazzband/tablib/commit/69abfc3ada5d754cb152119c0b4777043657cb6e', 'https://security.gentoo.org/glsa/201811-18', 'https://github.com/advisories/GHSA-gcr6-rf47-jrgf', 'https://talosintelligence.com/vulnerability_reports/TALOS-2017-0307', 'http://www.securityfocus.com/bid/99076', 'https://nvd.nist.gov/vuln/detail/CVE-2017-2810'}
null
{'https://github.com/jazzband/tablib/commit/69abfc3ada5d754cb152119c0b4777043657cb6e'}
{'https://github.com/jazzband/tablib/commit/69abfc3ada5d754cb152119c0b4777043657cb6e'}
GHSA
GHSA-vv2x-vrpj-qqpq
Cross-site scripting in Bleach
### Impact A [mutation XSS](https://cure53.de/fp170.pdf) affects users calling `bleach.clean` with all of: * `svg` or `math` in the allowed tags * `p` or `br` in allowed tags * `style`, `title`, `noscript`, `script`, `textarea`, `noframes`, `iframe`, or `xmp` in allowed tags * the keyword argument `strip_comments=False` Note: none of the above tags are in the default allowed tags and `strip_comments` defaults to `True`. ### Patches Users are encouraged to upgrade to bleach v3.3.0 or greater. Note: bleach v3.3.0 introduces a breaking change to escape HTML comments by default. ### Workarounds * modify `bleach.clean` calls to at least one of: * not allow the `style`, `title`, `noscript`, `script`, `textarea`, `noframes`, `iframe`, or `xmp` tag * not allow `svg` or `math` tags * not allow `p` or `br` tags * set `strip_comments=True` * A strong [Content-Security-Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) without `unsafe-inline` and `unsafe-eval` [`script-src`s](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src)) will also help mitigate the risk. ### References * https://bugzilla.mozilla.org/show_bug.cgi?id=1689399 * https://advisory.checkmarx.net/advisory/CX-2021-4303 * https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23980 * https://cure53.de/fp170.pdf ### Credits * Reported by [Yaniv Nizry](https://twitter.com/ynizry) from the CxSCA AppSec group at Checkmarx * Additional eject tags not mentioned in the original advisory and the CSP mitigation line being truncated in the revised advisory reported by [Michał Bentkowski](https://twitter.com/SecurityMB) at Securitum ### For more information If you have any questions or comments about this advisory: * Open an issue at [https://github.com/mozilla/bleach/issues](https://github.com/mozilla/bleach/issues) * Email us at [security@mozilla.org](mailto:security@mozilla.org)
{'CVE-2021-23980'}
2021-09-28T20:48:50Z
2021-02-02T17:58:40Z
MODERATE
0
{'CWE-79'}
{'https://bugzilla.mozilla.org/show_bug.cgi?id=1689399', 'https://github.com/mozilla/bleach/blob/79b7a3c5e56a09d1d323a5006afa59b56162eb13/CHANGES#L4', 'https://github.com/mozilla/bleach/commit/79b7a3c5e56a09d1d323a5006afa59b56162eb13', 'https://pypi.org/project/bleach/', 'https://cure53.de/fp170.pdf', 'https://github.com/advisories/GHSA-vv2x-vrpj-qqpq', 'https://github.com/mozilla/bleach/security/advisories/GHSA-vv2x-vrpj-qqpq'}
null
{'https://github.com/mozilla/bleach/commit/79b7a3c5e56a09d1d323a5006afa59b56162eb13'}
{'https://github.com/mozilla/bleach/commit/79b7a3c5e56a09d1d323a5006afa59b56162eb13'}
GHSA
GHSA-m52x-29pq-w3vv
Cross-Site Scripting in pannellum
Versions of `pannellum ` prior to 2.5.6 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize URLs for data URIs, which may allow attackers to execute arbitrary code in a victim's browser. ## Recommendation Upgrade to version 2.5.6 or later.
{'CVE-2019-16763'}
2022-04-19T19:02:23Z
2019-11-22T18:18:03Z
MODERATE
4.8
{'CWE-79'}
{'https://github.com/mpetroff/pannellum/security/advisories/GHSA-m52x-29pq-w3vv', 'https://github.com/advisories/GHSA-m52x-29pq-w3vv', 'https://nvd.nist.gov/vuln/detail/CVE-2019-16763', 'https://github.com/mpetroff/pannellum/commit/cc2f3d99953de59db908e0c6efd1c2c17f7c6914', 'https://www.npmjs.com/advisories/1418'}
null
{'https://github.com/mpetroff/pannellum/commit/cc2f3d99953de59db908e0c6efd1c2c17f7c6914'}
{'https://github.com/mpetroff/pannellum/commit/cc2f3d99953de59db908e0c6efd1c2c17f7c6914'}
GHSA
GHSA-9gjv-6qq6-v7qm
2FA bypass through deleting devices in wagtail-2fa
### Impact Any user with access to the CMS can view and delete other users' 2FA devices by going to the correct path. The user does not require special permissions in order to do so. By deleting the other user's device they can disable the target user's 2FA devices and potentially compromise the account if they figure out their password. ### Patches The problem has been patched in version 1.4.1. ### Workarounds There is no workaround for this issue. ### For more information If you have any questions or comments about this advisory: * Open an issue in [github.com/labd/wagtail-2fa](https://github.com/labd/wagtail-2fa) * Email us at [security@labdigital.nl](mailto:security@labdigital.nl)
{'CVE-2020-5240'}
2021-01-08T20:26:35Z
2020-03-13T21:18:55Z
HIGH
7.6
{'CWE-285'}
{'https://github.com/labd/wagtail-2fa/commit/ac23550d33b7436e90e3beea904647907eba5b74', 'https://github.com/advisories/GHSA-9gjv-6qq6-v7qm', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5240', 'https://github.com/labd/wagtail-2fa/security/advisories/GHSA-9gjv-6qq6-v7qm'}
null
{'https://github.com/labd/wagtail-2fa/commit/ac23550d33b7436e90e3beea904647907eba5b74'}
{'https://github.com/labd/wagtail-2fa/commit/ac23550d33b7436e90e3beea904647907eba5b74'}
GHSA
GHSA-ccxc-vr6p-4858
Improper Certificate Validation in Cosign
### Impact Cosign can be manipulated to claim that an entry for a signature exists in the Rekor transparency log even if it doesn't. This requires the attacker to have pull and push permissions for the signature in OCI. This can happen with both standard signing with a keypair and "keyless signing" with Fulcio. #### Signing with a keypair <details> To reproduce this vulnerability, create a keypair and sign an image. Don't store the signature in Rekor: ``` $ cosign generate-key-pair $ cosign sign --key cosign.key IMAGE ``` If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. To accomplish this, the attacker needs to: 1. Pull the signature image 2. Annotate the signature image with any valid Rekor bundle under the `dev.sigstore.cosign/bundle` annotation 3. Push the signature image back to OCI Verification then prints out the following: ``` $ cosign verify [--key] [IMAGE] Verification for [IMAGE] -- The following checks were performed on each of these signatures: - The cosign claims were validated - Existence of the claims in the transparency log was verified offline - The signatures were verified against the specified public key - Any certificates were verified against the Fulcio roots. […] ``` The claim that `Existence of the claims in the transparency log was verified offline` is inaccurate since an entry for this image doesn't exist in the log. The claim that `Any certificates were verified against the Fulcio roots.` is technically correct but since there were no certificates that should be explicitly called out. </details> #### "Keyless signing" with an OIDC flow <details> To reproduce this vulnerability, sign the image with a Fulcio identity. Don't store the signature in Rekor: ``` $ COSIGN_EXPERIMENTAL=1 cosign sign IMAGE [...] IMAGE appears to be a private repository, please confirm uploading to the transparency log at "https://rekor.sigstore.dev" [Y/N]: n ``` Then, create a keypair and sign the image again. Store an entry for the signature in Rekor: ``` $ cosign generate-key-pair $ COSIGN_EXPERIMENTAL=1 cosign sign --key cosign.key IMAGE Enter password for private key: IMAGE appears to be a private repository, please confirm uploading to the transparency log at "https://rekor.sigstore.dev" [Y/N]: y ``` If an attacker has access to the signature in OCI, they can manipulate cosign into believing the entry was stored in Rekor even though it wasn't. To accomplish this, the attacker needs to: 1. Pull the signature image 2. Copy the rekor bundle from the second signature into the first signature under the `dev.sigstore.cosign/bundle` annotation 3. Push the signature image back to OCI _Note: For this to work, both signatures must occur during the valid lifespan of the certificate (~20 minutes)._ Verification then prints out the following: ``` $ cosign verify [--key] [IMAGE] Verification for [IMAGE] -- The following checks were performed on each of these signatures: - The cosign claims were validated - Existence of the claims in the transparency log was verified offline - The signatures were verified against the specified public key - Any certificates were verified against the Fulcio roots. […] ``` The claim that `Existence of the claims in the transparency log was verified offline` is inaccurate since an entry for this image doesn't exist in the log. The claim that `Any certificates were verified against the Fulcio roots.` is technically correct but since there were no certificates that should be explicitly called out. </details> ### Patches The vulnerability has been patched in v1.5.2 of cosign. The `signature` in the `signedEntryTimestamp` provided by Rekor is now compared to the `signature` that is being verified. If these don't match, then an error is returned. If a valid bundle is copied to a different signature, verification should fail. Cosign output now only informs the user that certificates were verified if a certificate was in fact verified. ### Workarounds The only workaround is upgrading. ### For more information If you have any questions or comments about this advisory: * Open an issue in [cosign](https://github.com/sigstore/cosign) * Send us a message on [Slack](https://sigstore.slack.com/). Invite link [here](https://join.slack.com/t/sigstore/shared_invite/zt-mhs55zh0-XmY3bcfWn4XEyMqUUutbUQ). ### Thank you Thank you to @mtrmac for finding and reporting this vulnerability. Thank you to everyone who worked on fixing this: * @nsmith5 * @znewman01 * @dlorenc * @mattmoor * @priyawadhwa
{'CVE-2022-23649'}
2022-04-19T19:03:23Z
2022-02-22T19:34:09Z
LOW
3.3
{'CWE-295'}
{'https://github.com/sigstore/cosign/security/advisories/GHSA-ccxc-vr6p-4858', 'https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49', 'https://github.com/advisories/GHSA-ccxc-vr6p-4858', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23649', 'https://github.com/sigstore/cosign/releases/tag/v1.5.2'}
null
{'https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49'}
{'https://github.com/sigstore/cosign/commit/96d410a6580e4e81d24d112a0855c70ca3fb5b49'}
GHSA
GHSA-vgv5-cxvh-vfxh
Arbitrary code execution in clickhouse-driver
clickhouse-driver before 0.1.5 allows a malicious clickhouse server to trigger a crash or execute arbitrary code (on a database client) via a crafted server response, due to a buffer overflow.
{'CVE-2020-26759'}
2021-04-07T20:50:57Z
2021-04-07T20:50:57Z
CRITICAL
9.8
{'CWE-120'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-26759', 'https://github.com/advisories/GHSA-vgv5-cxvh-vfxh', 'https://github.com/mymarilyn/clickhouse-driver/commit/3e990547e064b8fca916b23a0f7d6fe8c63c7f6b', 'https://github.com/mymarilyn/clickhouse-driver/commit/d708ed548e1d6f254ba81a21de8ba543a53b5598'}
null
{'https://github.com/mymarilyn/clickhouse-driver/commit/3e990547e064b8fca916b23a0f7d6fe8c63c7f6b', 'https://github.com/mymarilyn/clickhouse-driver/commit/d708ed548e1d6f254ba81a21de8ba543a53b5598'}
{'https://github.com/mymarilyn/clickhouse-driver/commit/d708ed548e1d6f254ba81a21de8ba543a53b5598', 'https://github.com/mymarilyn/clickhouse-driver/commit/3e990547e064b8fca916b23a0f7d6fe8c63c7f6b'}
GHSA
GHSA-6jhm-4vmx-mr76
SQL injection in Moodle
A flaw was found in Moodle in versions 3.11 to 3.11.4. An SQL injection risk was identified in the h5p activity web service responsible for fetching user attempt data.
{'CVE-2022-0332'}
2022-02-02T16:11:17Z
2022-01-28T22:08:14Z
CRITICAL
9.8
{'CWE-89'}
{'https://github.com/advisories/GHSA-6jhm-4vmx-mr76', 'https://bugzilla.redhat.com/show_bug.cgi?id=2043661', 'https://github.com/moodle/moodle/commit/c7a62a8c82219b50589257f79021da1df1a76808', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0332', 'https://moodle.org/mod/forum/discuss.php?d=431099'}
null
{'https://github.com/moodle/moodle/commit/c7a62a8c82219b50589257f79021da1df1a76808'}
{'https://github.com/moodle/moodle/commit/c7a62a8c82219b50589257f79021da1df1a76808'}
GHSA
GHSA-pw3c-h7wp-cvhx
Improper Initialization in Pillow
Pillow is the friendly PIL (Python Imaging Library) fork. path_getbbox in path.c in Pillow before 9.0.0 improperly initializes ImagePath.Path.
{'CVE-2022-22815'}
2022-05-05T13:40:38Z
2022-01-12T20:07:43Z
CRITICAL
9.8
{'CWE-665'}
{'https://github.com/python-pillow/Pillow/blob/c5d9223a8b5e9295d15b5a9b1ef1dae44c8499f3/src/path.c#L331', 'https://www.debian.org/security/2022/dsa-5053', 'https://github.com/advisories/GHSA-pw3c-h7wp-cvhx', 'https://lists.debian.org/debian-lts-announce/2022/01/msg00018.html', 'https://pillow.readthedocs.io/en/stable/releasenotes/9.0.0.html#fixed-imagepath-path-array-handling', 'https://nvd.nist.gov/vuln/detail/CVE-2022-22815', 'https://github.com/python-pillow/Pillow/commit/c48271ab354db49cdbd740bc45e13be4f0f7993c'}
null
{'https://github.com/python-pillow/Pillow/commit/c48271ab354db49cdbd740bc45e13be4f0f7993c'}
{'https://github.com/python-pillow/Pillow/commit/c48271ab354db49cdbd740bc45e13be4f0f7993c'}
GHSA
GHSA-vx3p-948g-6vhq
Regular Expression Denial of Service (ReDoS)
npm `ssri` 5.2.2-6.0.1 and 7.0.0-8.0.0, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
{'CVE-2021-27290'}
2022-03-11T21:28:07Z
2021-03-19T21:24:36Z
HIGH
7.5
{'CWE-400'}
{'https://www.npmjs.com/package/ssri', 'https://github.com/yetingli/SaveResults/blob/main/pdf/ssri-redos.pdf', 'https://github.com/npm/ssri/commit/b30dfdb00bb94ddc49a25a85a18fb27afafdfbb1', 'https://github.com/npm/ssri/pull/20#issuecomment-842677644', 'https://github.com/advisories/GHSA-vx3p-948g-6vhq', 'https://github.com/npm/ssri/commit/76e223317d971f19e4db8191865bdad5edee40d2', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27290', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://npmjs.com', 'https://doyensec.com/resources/Doyensec_Advisory_ssri_redos.pdf'}
null
{'https://github.com/npm/ssri/commit/76e223317d971f19e4db8191865bdad5edee40d2', 'https://github.com/npm/ssri/commit/b30dfdb00bb94ddc49a25a85a18fb27afafdfbb1'}
{'https://github.com/npm/ssri/commit/b30dfdb00bb94ddc49a25a85a18fb27afafdfbb1', 'https://github.com/npm/ssri/commit/76e223317d971f19e4db8191865bdad5edee40d2'}
GHSA
GHSA-pq64-v7f5-gqh8
Regular Expression Denial of Service (ReDoS) in Pygments
In pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions. Some of the regular expressions have exponential or cubic worst-case complexity and are vulnerable to ReDoS. By crafting malicious input, an attacker can cause a denial of service.
{'CVE-2021-27291'}
2021-05-10T15:14:50Z
2021-03-29T16:33:03Z
MODERATE
7.5
{'CWE-400'}
{'https://github.com/pygments/pygments/commit/2e7e8c4a7b318f4032493773732754e418279a14', 'https://www.debian.org/security/2021/dsa-4889', 'https://lists.debian.org/debian-lts-announce/2021/05/msg00003.html', 'https://github.com/advisories/GHSA-pq64-v7f5-gqh8', 'https://gist.github.com/b-c-ds/b1a2cc0c68a35c57188575eb496de5ce', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GSJRFHALQ7E3UV4FFMFU2YQ6LUDHAI55/', 'https://lists.debian.org/debian-lts-announce/2021/03/msg00024.html', 'https://nvd.nist.gov/vuln/detail/CVE-2021-27291', 'https://www.debian.org/security/2021/dsa-4878', 'https://lists.debian.org/debian-lts-announce/2021/05/msg00006.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WSLD67LFGXOX2K5YNESSWAS4AGZIJTUQ/'}
null
{'https://github.com/pygments/pygments/commit/2e7e8c4a7b318f4032493773732754e418279a14'}
{'https://github.com/pygments/pygments/commit/2e7e8c4a7b318f4032493773732754e418279a14'}
GHSA
GHSA-jr9c-h74f-2v28
Improper Authorization in Gitea
Gitea 1.16.3 and prior is vulnerable to improper authorization. A patch is available and is anticipated to be part of the 1.16.4 release.
{'CVE-2022-0905'}
2022-03-28T22:24:30Z
2022-03-11T00:02:35Z
MODERATE
7.1
{'CWE-863', 'CWE-285'}
{'https://github.com/advisories/GHSA-jr9c-h74f-2v28', 'https://github.com/go-gitea/gitea/commit/1314f38b59748397b3429fb9bc9f9d6bac85d2f2', 'https://huntr.dev/bounties/8d221f92-b2b1-4878-bc31-66ff272e5ceb', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0905'}
null
{'https://github.com/go-gitea/gitea/commit/1314f38b59748397b3429fb9bc9f9d6bac85d2f2'}
{'https://github.com/go-gitea/gitea/commit/1314f38b59748397b3429fb9bc9f9d6bac85d2f2'}
GHSA
GHSA-4x2f-54wr-4hjg
Potential Zip Slip Vulnerability in baserCMS
There is a OS Command Injection Vulnerability on the management system of baserCMS. This is a vulnerability that needs to be addressed when the management system is used by an unspecified number of users. If you are eligible, please update to the new version as soon as possible. Target baserCMS 4.5.3 and earlier versions Vulnerability OS Command Injection Vulnerability. Countermeasures Update to the latest version of baserCMS Credits Daniele Scanu @SoterItSecurity
{'CVE-2021-41279'}
2021-12-01T18:29:32Z
2021-12-01T18:29:32Z
HIGH
7.7
{'CWE-22'}
{'https://github.com/advisories/GHSA-4x2f-54wr-4hjg', 'https://github.com/baserproject/basercms/security/advisories/GHSA-4x2f-54wr-4hjg', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41279', 'https://github.com/baserproject/basercms/commit/d8ab0a81a7bce35cc95ff7dff851a7e87a084336'}
null
{'https://github.com/baserproject/basercms/commit/d8ab0a81a7bce35cc95ff7dff851a7e87a084336'}
{'https://github.com/baserproject/basercms/commit/d8ab0a81a7bce35cc95ff7dff851a7e87a084336'}
GHSA
GHSA-2m7g-9q74-9m3q
Improper Certificate Validation in Apache Beam
The Apache Beam MongoDB connector in versions 2.10.0 to 2.16.0 has an option to disable SSL trust verification. However this configuration is not respected and the certificate verification disables trust verification in every case. This exclusion also gets registered globally which disables trust checking for any code running in the same JVM.
{'CVE-2020-1929'}
2021-08-25T21:06:45Z
2020-05-06T20:49:04Z
HIGH
7.5
{'CWE-295'}
{'https://lists.apache.org/thread.html/rdd0e85b71bf0274471b40fa1396d77f7b2d1165eaea4becbdc69aa04%40%3Cuser.beam.apache.org%3E', 'https://github.com/apache/beam/commit/a7dd23d95d2d214b4110781b5a28802bd43b834b', 'https://github.com/advisories/GHSA-2m7g-9q74-9m3q', 'https://nvd.nist.gov/vuln/detail/CVE-2020-1929'}
null
{'https://github.com/apache/beam/commit/a7dd23d95d2d214b4110781b5a28802bd43b834b'}
{'https://github.com/apache/beam/commit/a7dd23d95d2d214b4110781b5a28802bd43b834b'}
GHSA
GHSA-c7vm-f5p4-8fqh
Open redirect in Jupyter Notebook
[localhost](http://localhost:8888) ### Impact _What kind of vulnerability is it? Who is impacted?_ Open redirect vulnerability - a maliciously crafted link to a notebook server could redirect the browser to a different website. All notebook servers are technically affected, however, these maliciously crafted links can only be reasonably made for known notebook server hosts. A link to your notebook server may *appear* safe, but ultimately redirect to a spoofed server on the public internet. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Patched in notebook 6.1.5 ### References [OWASP page on open redirects](https://cheatsheetseries.owasp.org/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.html) ### For more information If you have any questions or comments about this advisory, or vulnerabilities to report, please email our security list [security@ipython.org](mailto:security@ipython.org). Credit: zhuonan li of Alibaba Application Security Team
{'CVE-2020-26215'}
2021-01-07T22:42:00Z
2020-11-18T21:06:36Z
MODERATE
4.4
{'CWE-601'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-26215', 'https://lists.debian.org/debian-lts-announce/2020/12/msg00004.html', 'https://github.com/jupyter/notebook/commit/3cec4bbe21756de9f0c4bccf18cf61d840314d74', 'https://github.com/jupyter/notebook/security/advisories/GHSA-c7vm-f5p4-8fqh', 'https://github.com/advisories/GHSA-c7vm-f5p4-8fqh'}
null
{'https://github.com/jupyter/notebook/commit/3cec4bbe21756de9f0c4bccf18cf61d840314d74'}
{'https://github.com/jupyter/notebook/commit/3cec4bbe21756de9f0c4bccf18cf61d840314d74'}
GHSA
GHSA-5xg3-j2j6-rcx4
Relative Path Traversal in git-delta
git-delta before 0.8.3 on Windows resolves an executable's pathname as a relative path from the current directory.
{'CVE-2021-36376'}
2021-09-09T16:46:43Z
2021-08-25T21:01:39Z
HIGH
7.8
{'CWE-427', 'CWE-23'}
{'https://vuln.ryotak.me/advisories/54', 'https://nvd.nist.gov/vuln/detail/CVE-2021-36376', 'https://github.com/dandavison/delta/commit/f01846bd443aaf92fdd5ac20f461beac3f6ee3fd', 'https://github.com/dandavison/delta/releases/tag/0.8.3', 'https://github.com/advisories/GHSA-5xg3-j2j6-rcx4'}
null
{'https://github.com/dandavison/delta/commit/f01846bd443aaf92fdd5ac20f461beac3f6ee3fd'}
{'https://github.com/dandavison/delta/commit/f01846bd443aaf92fdd5ac20f461beac3f6ee3fd'}
GHSA
GHSA-33vf-4xgg-9r58
HTTP Response Splitting (Early Hints) in Puma
### Impact If an application using Puma allows untrusted input in an early-hints header, an attacker can use a carriage return character to end the header and inject malicious content, such as additional headers or an entirely new response body. This vulnerability is known as [HTTP Response Splitting](https://owasp.org/www-community/attacks/HTTP_Response_Splitting) While not an attack in itself, response splitting is a vector for several other attacks, such as cross-site scripting (XSS). This is related to [CVE-2020-5247](https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v), which fixed this vulnerability but only for regular responses. ### Patches This has been fixed in 4.3.3 and 3.12.4. ### Workarounds Users can not allow untrusted/user input in the Early Hints response header. ### For more information If you have any questions or comments about this advisory: * Open an issue in [puma](https://github.com/puma/puma) * Email us a project maintainer. [Email addresses are listed in our Code of Conduct](https://github.com/puma/puma/blob/master/CODE_OF_CONDUCT.md#enforcement).
{'CVE-2020-5249'}
2021-01-08T20:28:11Z
2020-03-03T23:33:16Z
MODERATE
6.5
{'CWE-113'}
{'https://github.com/advisories/GHSA-33vf-4xgg-9r58', 'https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BMJ3CGZ3DLBJ5WUUKMI5ZFXFJQMXJZIK/', 'https://nvd.nist.gov/vuln/detail/CVE-2020-5249', 'https://github.com/puma/puma/security/advisories/GHSA-84j7-475p-hp8v', 'https://owasp.org/www-community/attacks/HTTP_Response_Splitting', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NJ3LL5F5QADB6LM46GXZETREAKZMQNRD/', 'https://github.com/puma/puma/security/advisories/GHSA-33vf-4xgg-9r58', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DIHVO3CQMU7BZC7FCTSRJ33YDNS3GFPK/'}
null
{'https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3'}
{'https://github.com/puma/puma/commit/c22712fc93284a45a93f9ad7023888f3a65524f3'}
GHSA
GHSA-8278-88vv-x98r
Execution of untrusted code through config file
### Impact It is possible to run arbitrary commands through the yaml.load() method. This could allow an attacker with local access to the host to run arbitrary code by running the application with a specially crafted YAML configuration file. ### Workarounds Manually adjust yaml.load() to yaml.safe_load() ### For more information If you have any questions or comments about this advisory: * Open an issue in [tenable/integration-jira-cloud](https://github.com/tenable/integration-jira-cloud/issues) * Email us at [vulnreport@tenable.com](mailto:vulnreport@tenable.com)
{'CVE-2021-21371'}
2022-04-19T19:02:50Z
2021-03-10T21:51:17Z
MODERATE
0
{'CWE-502'}
{'https://github.com/tenable/integration-jira-cloud/security/advisories/GHSA-8278-88vv-x98r', 'https://github.com/advisories/GHSA-8278-88vv-x98r', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21371', 'https://pypi.org/project/tenable-jira-cloud/', 'https://github.com/tenable/integration-jira-cloud/commit/f8c2095fd529e664e7fa25403a0a4a85bb3907d0', 'https://pyyaml.docsforge.com/master/documentation/#loading-yaml'}
null
{'https://github.com/tenable/integration-jira-cloud/commit/f8c2095fd529e664e7fa25403a0a4a85bb3907d0'}
{'https://github.com/tenable/integration-jira-cloud/commit/f8c2095fd529e664e7fa25403a0a4a85bb3907d0'}
GHSA
GHSA-43f8-2h32-f4cj
Regular Expression Denial of Service in hosted-git-info
The npm package `hosted-git-info` before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity
{'CVE-2021-23362'}
2022-03-18T20:25:44Z
2021-05-06T16:10:39Z
MODERATE
5.3
{'CWE-400'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-23362', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1088356', 'https://github.com/npm/hosted-git-info/commit/8d4b3697d79bcd89cdb36d1db165e3696c783a01', 'https://snyk.io/vuln/SNYK-JS-HOSTEDGITINFO-1088355', 'https://github.com/npm/hosted-git-info/commit/bede0dc38e1785e732bf0a48ba6f81a4a908eba3', 'https://github.com/npm/hosted-git-info/pull/76', 'https://github.com/advisories/GHSA-43f8-2h32-f4cj', 'https://github.com/npm/hosted-git-info/commits/v2', 'https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf', 'https://github.com/npm/hosted-git-info/commit/29adfe5ef789784c861b2cdeb15051ec2ba651a7'}
null
{'https://github.com/npm/hosted-git-info/commit/29adfe5ef789784c861b2cdeb15051ec2ba651a7', 'https://github.com/npm/hosted-git-info/commit/8d4b3697d79bcd89cdb36d1db165e3696c783a01', 'https://github.com/npm/hosted-git-info/commit/bede0dc38e1785e732bf0a48ba6f81a4a908eba3'}
{'https://github.com/npm/hosted-git-info/commit/bede0dc38e1785e732bf0a48ba6f81a4a908eba3', 'https://github.com/npm/hosted-git-info/commit/8d4b3697d79bcd89cdb36d1db165e3696c783a01', 'https://github.com/npm/hosted-git-info/commit/29adfe5ef789784c861b2cdeb15051ec2ba651a7'}
GHSA
GHSA-67mq-h2r9-rh2m
Prototype pollution in multi-ini
This affects the package multi-ini before 2.1.2. It is possible to pollute an object's prototype by specifying the constructor.proto object as part of an array. This is a bypass of CVE-2020-28448.
{'CVE-2020-28460'}
2021-04-13T15:23:41Z
2021-04-13T15:23:41Z
HIGH
5.6
{'CWE-1321'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-28460', 'https://github.com/advisories/GHSA-67mq-h2r9-rh2m', 'https://github.com/evangelion1204/multi-ini/commit/6b2212b2ce152c19538a2431415f72942c5a1bde', 'https://snyk.io/vuln/SNYK-JS-MULTIINI-1053229'}
null
{'https://github.com/evangelion1204/multi-ini/commit/6b2212b2ce152c19538a2431415f72942c5a1bde'}
{'https://github.com/evangelion1204/multi-ini/commit/6b2212b2ce152c19538a2431415f72942c5a1bde'}
GHSA
GHSA-x28w-hvwc-mp75
Static Code Injection in Microweber
Microweber is a new generation CMS with drag and drop. Prior to version 1.3, Microweber is vulnerable to static code injection.
{'CVE-2022-0895'}
2022-03-25T17:18:06Z
2022-03-11T00:02:35Z
HIGH
7.7
{'CWE-94', 'CWE-96'}
{'https://github.com/microweber/microweber/commit/b2baab6e582b2efe63788d367a2bb61a2fa26470', 'https://huntr.dev/bounties/3c070828-fd00-476c-be33-9c877172363d', 'https://github.com/advisories/GHSA-x28w-hvwc-mp75', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0895'}
null
{'https://github.com/microweber/microweber/commit/b2baab6e582b2efe63788d367a2bb61a2fa26470'}
{'https://github.com/microweber/microweber/commit/b2baab6e582b2efe63788d367a2bb61a2fa26470'}
GHSA
GHSA-2frx-j9hj-6c65
User enumeration in authentication mechanisms
Description ----------- The ability to enumerate users was possible without relevant permissions due to different exception messages depending on whether the user existed or not. Resolution ---------- We now ensure that a generic message is returned whether the user exists or not if the password is invalid or if the user does not exist. The patch for this issue is available [here](https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7) for branch 2.10.x and 2.x. Credits ------- I would like to thank James Isaac and Mathias Brodala for reporting the issue and Robin Chalas for fixing the issue.
null
2022-04-19T19:02:57Z
2021-05-17T20:52:21Z
LOW
0
{'CWE-200'}
{'https://github.com/lexik/LexikJWTAuthenticationBundle/security/advisories/GHSA-2frx-j9hj-6c65', 'https://github.com/advisories/GHSA-2frx-j9hj-6c65', 'https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7'}
null
{'https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7'}
{'https://github.com/lexik/LexikJWTAuthenticationBundle/commit/a175d6dab968d93e96a3e4f80c495435f71d5eb7'}
GHSA
GHSA-xcqr-9h24-vrgw
Improper Restriction of Excessive Authentication Attempts in Argo API
As of v1.5.0, the Argo API does not implement anti-automation measures such as rate limiting, account lockouts, or other anti-bruteforce measures. Attackers can submit an unlimited number of authentication attempts without consequence.
{'CVE-2020-8827'}
2021-07-26T21:19:37Z
2021-07-26T21:19:37Z
HIGH
7.5
{'CWE-307'}
{'https://www.soluble.ai/blog/argo-cves-2020', 'https://github.com/advisories/GHSA-xcqr-9h24-vrgw', 'https://github.com/argoproj/argo-cd/pull/3369', 'https://nvd.nist.gov/vuln/detail/CVE-2020-8827', 'https://github.com/argoproj/argo-cd/pull/3404', 'https://argoproj.github.io/argo-cd/security_considerations/', 'https://github.com/argoproj/argo/releases', 'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1', 'https://argoproj.github.io/argo-cd/operator-manual/user-management/#disable-admin-user'}
null
{'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'}
{'https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1'}
GHSA
GHSA-9j2c-x8qm-qmjq
SQL injection in Tortoise ORM
### Impact Various forms of SQL injection has been found, for MySQL and when filtering or doing mass-updates on char/text fields. SQLite & PostgreSQL was only affected when filtering with ``contains``, ``starts_with`` or ``ends_with`` filters (and their case-insensitive counterparts) ### Patches Please upgrade to 0.15.23+ or 0.16.6+ ### For more information If you have any questions or comments about this advisory: * Open an issue in [Github](https://github.com/tortoise/tortoise-orm/issues) * Chat to us on [Gitter](https://gitter.im/tortoise/community)
{'CVE-2020-11010'}
2021-01-08T20:21:41Z
2020-04-20T21:31:23Z
MODERATE
6.3
{'CWE-89'}
{'https://github.com/advisories/GHSA-9j2c-x8qm-qmjq', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11010', 'https://github.com/tortoise/tortoise-orm/commit/91c364053e0ddf77edc5442914c6f049512678b3', 'https://github.com/tortoise/tortoise-orm/security/advisories/GHSA-9j2c-x8qm-qmjq'}
null
{'https://github.com/tortoise/tortoise-orm/commit/91c364053e0ddf77edc5442914c6f049512678b3'}
{'https://github.com/tortoise/tortoise-orm/commit/91c364053e0ddf77edc5442914c6f049512678b3'}
GHSA
GHSA-vc5r-xfc4-4x22
Cross-site Scripting in Pimcore Datahub
Pimcore Datahub prior to 1.2.4 is vulnerable to stored cross-site scripting. An admin user accessing Datahub triggers the attack, which may result in the user's cookie being stolen.
{'CVE-2022-0955'}
2022-04-05T20:53:20Z
2022-03-25T00:00:33Z
MODERATE
4.8
{'CWE-79'}
{'https://nvd.nist.gov/vuln/detail/CVE-2022-0955', 'https://github.com/advisories/GHSA-vc5r-xfc4-4x22', 'https://github.com/pimcore/data-hub/commit/15d5b57af2466eebd3bbc531ead5dafa35d0a36e', 'https://huntr.dev/bounties/708971a6-1e6c-4c51-a411-255caeba51df'}
null
{'https://github.com/pimcore/data-hub/commit/15d5b57af2466eebd3bbc531ead5dafa35d0a36e'}
{'https://github.com/pimcore/data-hub/commit/15d5b57af2466eebd3bbc531ead5dafa35d0a36e'}
GHSA
GHSA-5phf-pp7p-vc2r
Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection
### Impact Users who are using an HTTPS proxy to issue HTTPS requests and haven't configured their own SSLContext via `proxy_config`. Only the default SSLContext is impacted. ### Patches [urllib3 >=1.26.4 has the issue resolved](https://github.com/urllib3/urllib3/releases/tag/1.26.4). urllib3<1.26 is not impacted due to not supporting HTTPS requests via HTTPS proxies. ### Workarounds Upgrading is recommended as this is a minor release and not likely to break current usage. Configuring an `SSLContext` with `check_hostname=True` and passing via `proxy_config` instead of relying on the default `SSLContext` ### For more information If you have any questions or comments about this advisory: * Email us at [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)
{'CVE-2021-28363'}
2022-04-19T19:02:50Z
2021-03-19T19:42:11Z
MODERATE
6.5
{'CWE-295'}
{'https://github.com/advisories/GHSA-5phf-pp7p-vc2r', 'https://pypi.org/project/urllib3/1.26.4/', 'https://nvd.nist.gov/vuln/detail/CVE-2021-28363', 'https://github.com/urllib3/urllib3/releases/tag/1.26.4', 'https://github.com/urllib3/urllib3/security/advisories/GHSA-5phf-pp7p-vc2r', 'https://github.com/urllib3/urllib3/commit/8d65ea1ecf6e2cdc27d42124e587c1b83a3118b0', 'https://github.com/pypa/advisory-db/tree/main/vulns/urllib3/PYSEC-2021-59.yaml', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://github.com/urllib3/urllib3/blob/main/CHANGES.rst#1264-2021-03-15', 'https://security.gentoo.org/glsa/202107-36', 'https://github.com/urllib3/urllib3/commits/main', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4S65ZQVZ2ODGB52IC7VJDBUK4M5INCXL/'}
null
{'https://github.com/urllib3/urllib3/commit/8d65ea1ecf6e2cdc27d42124e587c1b83a3118b0'}
{'https://github.com/urllib3/urllib3/commit/8d65ea1ecf6e2cdc27d42124e587c1b83a3118b0'}
GHSA
GHSA-xpxm-pf7g-2534
Cross-site scripting in media2click
The media2click (aka 2 Clicks for External Media) extension 1.x before 1.3.3 for TYPO3 allows XSS by a backend user account.
{'CVE-2021-31778'}
2021-06-08T20:11:52Z
2021-06-08T20:11:52Z
MODERATE
6.4
{'CWE-79'}
{'https://packagist.org/packages/amazing/media2click', 'https://typo3.org/security/advisory/typo3-ext-sa-2021-004', 'https://github.com/advisories/GHSA-xpxm-pf7g-2534', 'https://nvd.nist.gov/vuln/detail/CVE-2021-31778', 'https://github.com/ghermens/media2click/commit/3c4e413fbc7d35c47212e754c24d5070637a11a3'}
null
{'https://github.com/ghermens/media2click/commit/3c4e413fbc7d35c47212e754c24d5070637a11a3'}
{'https://github.com/ghermens/media2click/commit/3c4e413fbc7d35c47212e754c24d5070637a11a3'}
GHSA
GHSA-8v38-pw62-9cw2
Incorrect returned href via an '@' sign but no user info and hostname
A specially crafted URL with an '@' sign but empty user info and no hostname, when parsed with url-parse, url-parse will return the incorrect href. In particular, ````` parse(\"http://@/127.0.0.1\") ````` Will return: ````` { slashes: true, protocol: 'http:', hash: '', query: '', pathname: '/127.0.0.1', auth: '', host: '', port: '', hostname: '', password: '', username: '', origin: 'null', href: 'http:///127.0.0.1' } ````` If the 'hostname' or 'origin' attributes of the output from url-parse are used in security decisions and the final 'href' attribute of the output is then used to make a request, the decision may be incorrect.
{'CVE-2022-0639'}
2022-04-19T19:03:27Z
2022-02-18T00:00:33Z
MODERATE
6.5
{'CWE-639'}
{'https://huntr.dev/bounties/83a6bc9a-b542-4a38-82cd-d995a1481155', 'https://github.com/unshiftio/url-parse/commit/ef45a1355375a8244063793a19059b4f62fc8788', 'https://nvd.nist.gov/vuln/detail/CVE-2022-0639', 'https://github.com/advisories/GHSA-8v38-pw62-9cw2'}
null
{'https://github.com/unshiftio/url-parse/commit/ef45a1355375a8244063793a19059b4f62fc8788'}
{'https://github.com/unshiftio/url-parse/commit/ef45a1355375a8244063793a19059b4f62fc8788'}
GHSA
GHSA-7257-96vg-qf6x
Remote Code Execution in Red Discord Bot
### Impact A RCE exploit has been discovered in the Streams module: this exploit allows Discord users with specifically crafted "going live" messages to inject code into the Streams module's going live message. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information. ### Patches This critical exploit has been fixed on version ``3.3.12`` & ``3.4``. ### Workarounds Unloading the Streams module with ``unload streams`` can render this exploit not accessible. We still highly recommend updating to ``3.3.12`` or ``3.4`` to completely patch this issue. ### References * https://github.com/Cog-Creators/Red-DiscordBot/pull/4183 ### For more information If you have any questions or comments about this advisory: * Open an issue in [Cog-Creators/Red-DiscordBot](https://github.com/Cog-Creators/Red-DiscordBot) * Over on our [Discord server](https://discord.gg/red)
{'CVE-2020-15147'}
2022-04-19T19:02:33Z
2020-08-21T17:03:24Z
HIGH
8.5
{'CWE-94', 'CWE-74'}
{'https://github.com/advisories/GHSA-7257-96vg-qf6x', 'https://github.com/Cog-Creators/Red-DiscordBot/security/advisories/GHSA-7257-96vg-qf6x', 'https://github.com/Cog-Creators/Red-DiscordBot/pull/4183/commits/e269ea0d3bc88417163c18431b1df38a9be92bfc', 'https://github.com/Cog-Creators/Red-DiscordBot/pull/4183', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15147'}
null
{'https://github.com/Cog-Creators/Red-DiscordBot/pull/4183/commits/e269ea0d3bc88417163c18431b1df38a9be92bfc'}
{'https://github.com/Cog-Creators/Red-DiscordBot/pull/4183/commits/e269ea0d3bc88417163c18431b1df38a9be92bfc'}
GHSA
GHSA-mx9v-gmh4-mgqw
High severity vulnerability that affects com.fasterxml.jackson.core:jackson-databind
FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the openjpa class from polymorphic deserialization.
{'CVE-2018-19361'}
2021-06-10T22:10:26Z
2019-01-04T19:07:01Z
CRITICAL
9.8
{'CWE-502'}
{'http://www.securityfocus.com/bid/107985', 'https://access.redhat.com/errata/RHSA-2019:3140', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://lists.apache.org/thread.html/ff8dcfe29377088ab655fda9d585dccd5b1f07fabd94ae84fd60a7f8@%3Ccommits.pulsar.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:2804', 'https://lists.apache.org/thread.html/rf1bbc0ea4a9f014cf94df9a12a6477d24a27f52741dbc87f2fd52ff2@%3Cissues.geode.apache.org%3E', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/03/msg00005.html', 'https://access.redhat.com/errata/RHBA-2019:0959', 'https://access.redhat.com/errata/RHSA-2019:1797', 'https://seclists.org/bugtraq/2019/May/68', 'https://access.redhat.com/errata/RHSA-2019:4037', 'https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.8', 'https://www.debian.org/security/2019/dsa-4452', 'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b', 'https://lists.apache.org/thread.html/c70da3cb6e3f03e0ad8013e38b6959419d866c4a7c80fdd34b73f25c@%3Ccommits.pulsar.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20190530-0003/', 'https://access.redhat.com/errata/RHSA-2019:2858', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://access.redhat.com/errata/RHSA-2019:1822', 'https://nvd.nist.gov/vuln/detail/CVE-2018-19361', 'https://www.oracle.com/technetwork/security-advisory/cpuapr2019-5072813.html', 'https://github.com/FasterXML/jackson-databind/issues/2186', 'https://access.redhat.com/errata/RHSA-2019:0782', 'https://access.redhat.com/errata/RHSA-2019:0877', 'https://access.redhat.com/errata/RHSA-2019:3149', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://lists.apache.org/thread.html/r1b103833cb5bc8466e24ff0ecc5e75b45a705334ab6a444e64e840a0@%3Cissues.bookkeeper.apache.org%3E', 'https://lists.apache.org/thread.html/37e1ed724a1b0e5d191d98c822c426670bdfde83804567131847d2a3@%3Cdevnull.infra.apache.org%3E', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://github.com/advisories/GHSA-mx9v-gmh4-mgqw', 'https://access.redhat.com/errata/RHSA-2019:3002', 'https://issues.apache.org/jira/browse/TINKERPOP-2121', 'https://access.redhat.com/errata/RHSA-2019:1782', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://access.redhat.com/errata/RHSA-2019:3892', 'https://access.redhat.com/errata/RHSA-2019:1823'}
null
{'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'}
{'https://github.com/FasterXML/jackson-databind/commit/42912cac4753f3f718ece875e4d486f8264c2f2b'}
GHSA
GHSA-fhpf-pp6p-55qc
Unsafe handling of user-specified cookies in treq
### Impact Treq's request methods (`treq.get`, `treq.post`, `HTTPClient.request`, `HTTPClient.get`, etc.) accept cookies as a dictionary, for example: ```py treq.get('https://example.com/', cookies={'session': '1234'}) ``` Such cookies are not bound to a single domain, and are therefore sent to *every* domain ("supercookies"). This can potentially cause sensitive information to leak upon an HTTP redirect to a different domain., e.g. should `https://example.com` redirect to `http://cloudstorageprovider.com` the latter will receive the cookie `session`. ### Patches Treq 2021.1.0 and later bind cookies given to request methods (`treq.request`, `treq.get`, `HTTPClient.request`, `HTTPClient.get`, etc.) to the origin of the *url* parameter. ### Workarounds Instead of passing a dictionary as the *cookies* argument, pass a `http.cookiejar.CookieJar` instance with properly domain- and scheme-scoped cookies in it: ```py from http.cookiejar import CookieJar from requests.cookies import create_cookie jar = CookieJar() jar.add_cookie( create_cookie( name='session', value='1234', domain='example.com', secure=True, ), ) client = HTTPClient(cookies=jar) client.get('https://example.com/') ``` ### References * Originally reported at [huntr.dev](https://huntr.dev/bounties/3c9204fc-a3d1-4441-8599-924c5f57e7ae/?token=06d930e37046c914bcb037e85cc227dc7b510b475989fc69837566562ba899277d46b0fb4b1e21cdcb6ddc1b7d9b1ded632cf3a3551ecb89afca16a63b34641284b50479d5195bba2ac09b116f3dd4fad27f54404c2de922c05c8c8b744aec27bb4d4d198cb8b3abf479af0c2d5fbaa10412da7922594ac3eb39) * A related issue in the handling of HTTP basic authentication was addressed in Twisted 22.1 ([GHSA-92x2-jw7w-xvvx](https://github.com/twisted/twisted/security/advisories/GHSA-92x2-jw7w-xvvx), CVE-2022-21712).
{'CVE-2022-23607'}
2022-03-25T19:28:28Z
2022-02-01T00:43:38Z
MODERATE
6.5
{'CWE-200', 'CWE-601'}
{'https://nvd.nist.gov/vuln/detail/CVE-2022-23607', 'https://github.com/twisted/treq/commit/1da6022cc880bbcff59321abe02bf8498b89efb2', 'https://github.com/twisted/treq/security/advisories/GHSA-fhpf-pp6p-55qc', 'https://huntr.dev/bounties/3c9204fc-a3d1-4441-8599-924c5f57e7ae/?token=06d930e37046c914bcb037e85cc227dc7b510b475989fc69837566562ba899277d46b0fb4b1e21cdcb6ddc1b7d9b1ded632cf3a3551ecb89afca16a63b34641284b50479d5195bba2ac09b116f3dd4fad27f54404c2de922c05c8c8b744aec27bb4d4d198cb8b3abf479af0c2d5fbaa10412da7922594ac3eb39', 'https://github.com/advisories/GHSA-fhpf-pp6p-55qc', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00025.html', 'https://github.com/twisted/treq/releases/tag/release-22.1.0'}
null
{'https://github.com/twisted/treq/commit/1da6022cc880bbcff59321abe02bf8498b89efb2'}
{'https://github.com/twisted/treq/commit/1da6022cc880bbcff59321abe02bf8498b89efb2'}
GHSA
GHSA-7wpw-2hjm-89gp
Prototype Pollution in merge
All versions of package merge <2.1.1 are vulnerable to Prototype Pollution via _recursiveMerge .
{'CVE-2020-28499'}
2021-05-18T21:54:59Z
2021-05-04T20:18:47Z
HIGH
7.3
{'CWE-915'}
{'https://github.com/advisories/GHSA-7wpw-2hjm-89gp', 'https://snyk.io/vuln/SNYK-JAVA-ORGWEBJARSNPM-1071049', 'https://github.com/yeikos/js.merge/blob/master/src/index.ts%23L64', 'https://nvd.nist.gov/vuln/detail/CVE-2020-28499', 'https://vuldb.com/?id.170146', 'https://github.com/yeikos/js.merge/blob/56ca75b2dd0f2820f1e08a49f62f04bbfb8c5f8f/src/index.ts#L64', 'https://snyk.io/vuln/SNYK-JS-MERGE-1042987', 'https://github.com/yeikos/js.merge/commit/7b0ddc2701d813f2ba289b32d6a4b9d4cc235fb4'}
null
{'https://github.com/yeikos/js.merge/commit/7b0ddc2701d813f2ba289b32d6a4b9d4cc235fb4'}
{'https://github.com/yeikos/js.merge/commit/7b0ddc2701d813f2ba289b32d6a4b9d4cc235fb4'}
GHSA
GHSA-wjm3-fq3r-5x46
Denial of service
GJSON <1.6.5 allows attackers to cause a denial of service (remote) via crafted JSON.
{'CVE-2020-36066'}
2021-05-18T21:07:54Z
2021-05-18T21:07:54Z
MODERATE
7.5
{'CWE-400'}
{'https://github.com/advisories/GHSA-wjm3-fq3r-5x46', 'https://github.com/tidwall/match/commit/c2f534168b739a7ec1821a33839fb2f029f26bbc', 'https://github.com/tidwall/gjson/issues/195', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36066', 'https://github.com/tidwall/gjson/issues/195#issuecomment-755303148'}
null
{'https://github.com/tidwall/match/commit/c2f534168b739a7ec1821a33839fb2f029f26bbc'}
{'https://github.com/tidwall/match/commit/c2f534168b739a7ec1821a33839fb2f029f26bbc'}
GHSA
GHSA-772p-x54p-hjrv
Division by zero in `Conv3D`
### Impact A malicious user could trigger a division by 0 in `Conv3D` implementation: ```python import tensorflow as tf input_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32) filter_tensor = tf.constant([], shape=[0, 0, 0, 0, 0], dtype=tf.float32) tf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 56, 56, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 23, 1]) ``` The [implementation](https://github.com/tensorflow/tensorflow/blob/42033603003965bffac51ae171b51801565e002d/tensorflow/core/kernels/conv_ops_3d.cc#L143-L145) does a modulo operation based on user controlled input: ```cc const int64 out_depth = filter.dim_size(4); OP_REQUIRES(context, in_depth % filter_depth == 0, ...); ``` Thus, when `filter` has a 0 as the fifth element, this results in a division by 0. Additionally, if the shape of the two tensors is not valid, an Eigen assertion can be triggered, resulting in a program crash: ```python import tensorflow as tf input_tensor = tf.constant([], shape=[2, 2, 2, 2, 0], dtype=tf.float32) filter_tensor = tf.constant([], shape=[0, 0, 2, 6, 2], dtype=tf.float32) tf.raw_ops.Conv3D(input=input_tensor, filter=filter_tensor, strides=[1, 56, 39, 34, 1], padding='VALID', data_format='NDHWC', dilations=[1, 1, 1, 1, 1]) ``` The shape of the two tensors must follow the constraints specified in the [op description](https://www.tensorflow.org/api_docs/python/tf/raw_ops/Conv3D). ### Patches We have patched the issue in GitHub commit [799f835a3dfa00a4d852defa29b15841eea9d64f](https://github.com/tensorflow/tensorflow/commit/799f835a3dfa00a4d852defa29b15841eea9d64f). 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-29517'}
2021-05-21T14:21:01Z
2021-05-21T14:21:01Z
LOW
2.5
{'CWE-369'}
{'https://github.com/advisories/GHSA-772p-x54p-hjrv', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-772p-x54p-hjrv', 'https://github.com/tensorflow/tensorflow/commit/799f835a3dfa00a4d852defa29b15841eea9d64f', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29517'}
null
{'https://github.com/tensorflow/tensorflow/commit/799f835a3dfa00a4d852defa29b15841eea9d64f'}
{'https://github.com/tensorflow/tensorflow/commit/799f835a3dfa00a4d852defa29b15841eea9d64f'}
GHSA
GHSA-p463-639r-q9g9
High severity vulnerability that affects dragonfly
The Dragonfly gem 0.7 before 0.8.6 and 0.9.x before 0.9.13 for Ruby, when used with Ruby on Rails, allows remote attackers to execute arbitrary code via a crafted request.
{'CVE-2013-1756'}
2021-09-15T21:29:21Z
2017-10-24T18:33:37Z
HIGH
0
{'CWE-94'}
{'http://secunia.com/advisories/52380', 'https://github.com/markevans/dragonfly/commit/a8775aacf9e5c81cf11bec34b7afa7f27ddfe277', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/82476', 'https://nvd.nist.gov/vuln/detail/CVE-2013-1756', 'https://github.com/advisories/GHSA-p463-639r-q9g9', 'http://www.securityfocus.com/bid/58225', 'https://groups.google.com/forum/?fromgroups=#!topic/dragonfly-users/3c3WIU3VQTo'}
null
{'https://github.com/markevans/dragonfly/commit/a8775aacf9e5c81cf11bec34b7afa7f27ddfe277'}
{'https://github.com/markevans/dragonfly/commit/a8775aacf9e5c81cf11bec34b7afa7f27ddfe277'}
GHSA
GHSA-6956-83fg-5wc5
Prototype Pollution in set-in
The package set-in before 2.0.3 is vulnerable to Prototype Pollution via the `setIn` method, as it allows an attacker to merge object prototypes into it. **Note:** This vulnerability derives from an incomplete fix of [CVE-2020-28273](https://security.snyk.io/vuln/SNYK-JS-SETIN-1048049)
{'CVE-2022-25354'}
2022-03-29T21:05:16Z
2022-03-18T00:01:11Z
CRITICAL
9.8
{'CWE-1321'}
{'https://github.com/ahdinosaur/set-in/commit/6bad255961d379e4b1f5fbc52ef9dc8420816f24', 'https://github.com/advisories/GHSA-6956-83fg-5wc5', 'https://snyk.io/vuln/SNYK-JS-SETIN-2388571', 'https://nvd.nist.gov/vuln/detail/CVE-2022-25354', 'https://github.com/ahdinosaur/set-in/blob/dfc226d95cce8129de6708661e06e0c2c06f3490/index.js%23L5'}
null
{'https://github.com/ahdinosaur/set-in/commit/6bad255961d379e4b1f5fbc52ef9dc8420816f24'}
{'https://github.com/ahdinosaur/set-in/commit/6bad255961d379e4b1f5fbc52ef9dc8420816f24'}
GHSA
GHSA-p63h-7hw8-5cw4
Cross-Site Request Forgery in OpenNMS Horizon
In OpenNMS Horizon, versions opennms-1-0-stable through opennms-27.1.1; OpenNMS Meridian, versions meridian-foundation-2015.1.0-1 through meridian-foundation-2019.1.18-1; meridian-foundation-2020.1.0-1 through meridian-foundation-2020.1.6-1 are vulnerable to CSRF, due to no CSRF protection, and since there is no validation of an existing user name while renaming a user. As a result, privileges of the renamed user are being overwritten by the old user and the old user is being deleted from the user list.
{'CVE-2021-25930'}
2021-05-28T22:25:42Z
2021-05-25T18:46:49Z
MODERATE
4.3
{'CWE-352'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-25930', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25930', 'https://github.com/advisories/GHSA-p63h-7hw8-5cw4', 'https://github.com/OpenNMS/opennms/commit/607151ea8f90212a3fb37c977fa57c7d58d26a84', 'https://github.com/OpenNMS/opennms/commit/eb08b5ed4c5548f3e941a1f0d0363ae4439fa98c'}
null
{'https://github.com/OpenNMS/opennms/commit/eb08b5ed4c5548f3e941a1f0d0363ae4439fa98c', 'https://github.com/OpenNMS/opennms/commit/607151ea8f90212a3fb37c977fa57c7d58d26a84'}
{'https://github.com/OpenNMS/opennms/commit/eb08b5ed4c5548f3e941a1f0d0363ae4439fa98c', 'https://github.com/OpenNMS/opennms/commit/607151ea8f90212a3fb37c977fa57c7d58d26a84'}
GHSA
GHSA-mrq4-7ch7-2465
Server Side Twig Template Injection
PrestaShop is an Open Source e-commerce platform. Starting with version 1.7.0.0 and ending with version 1.7.8.3, an attacker is able to inject twig code inside the back office when using the legacy layout. The problem is fixed in version 1.7.8.3. There are no known workarounds.
{'CVE-2022-21686'}
2022-04-19T19:03:20Z
2022-01-27T18:32:47Z
CRITICAL
9
{'CWE-94'}
{'https://nvd.nist.gov/vuln/detail/CVE-2022-21686', 'https://github.com/PrestaShop/PrestaShop/releases/tag/1.7.8.3', 'https://github.com/PrestaShop/PrestaShop/security/advisories/GHSA-mrq4-7ch7-2465', 'https://github.com/PrestaShop/PrestaShop/commit/d02b469ec365822e6a9f017e57f588966248bf21', 'https://github.com/advisories/GHSA-mrq4-7ch7-2465'}
null
{'https://github.com/PrestaShop/PrestaShop/commit/d02b469ec365822e6a9f017e57f588966248bf21'}
{'https://github.com/PrestaShop/PrestaShop/commit/d02b469ec365822e6a9f017e57f588966248bf21'}
GHSA
GHSA-rw98-5846-pqhx
Open redirect in microweber
Open Redirect in Packagist microweber/microweber prior to 1.2.11.
{'CVE-2022-0597'}
2022-02-24T13:56:27Z
2022-02-16T00:01:45Z
MODERATE
6.1
{'CWE-601'}
{'https://nvd.nist.gov/vuln/detail/CVE-2022-0597', 'https://github.com/advisories/GHSA-rw98-5846-pqhx', 'https://github.com/microweber/microweber/commit/acfc6a581d1ea86096d1b0ecd8a0eec927c0e9b2', 'https://huntr.dev/bounties/68c22eab-cc69-4e9f-bcb6-2df3db626813'}
null
{'https://github.com/microweber/microweber/commit/acfc6a581d1ea86096d1b0ecd8a0eec927c0e9b2'}
{'https://github.com/microweber/microweber/commit/acfc6a581d1ea86096d1b0ecd8a0eec927c0e9b2'}
GHSA
GHSA-8v99-48m9-c8pm
Incorrect Authorization in imgcrypt
Imgcrypt implements a function `CheckAuthorization()` that is supposed to check whether a user is authorized to access an encrypted image given the keys that the user has provided on the command line that would enable decryption of the image. The check is to prevent that a user can start a container from an image that has previously been decrypted by another user on the same system and therefore a decrypted version of the image layers may be already available in the cache locally. The failure occurs when an image with a ManifestList is used and the architecture of the local host is not the first one in the ManifestList. In the version prior to the fix, only the first architecture in the list was tested, which may not have its layers available locally (were not pulled) since it cannot be run on the host architecture. Therefore, the verdict on unavailable layers was that the image could be run anticipating that image run failure would occur later due to the layers not being available. However, this verdict to allow the image to run lead to other architectures in the ManifestList be able to run an image without providing keys if that image had previously been decrypted. The fixed version now skips over irrelevant architectures and tests the Manifest of the local architecture, if available. Known projects that use the `CheckAuthorization()` of imgcrypt is for example the ctr-enc client tool provided by imgcrypt. In this implementation, the call to `CheckAuthorization()` is used on the client side and could therefore also be easily circumvented by a modified client tool not calling this function. In relation to the vulnerability in ctr-enc, affected environments would have to allow different users to invoke ctr-enc indirectly using some sort of management stack that gives user indirect access to ctr-enc. The patch has been applied to imgcrypt v1.1.4. Workarounds may include usage of different namespaces for each remote user.
{'CVE-2022-24778'}
2022-04-13T03:57:34Z
2022-03-28T19:33:44Z
HIGH
7.5
{'CWE-863'}
{'https://github.com/containerd/imgcrypt/issues/69', 'https://github.com/advisories/GHSA-8v99-48m9-c8pm', 'https://github.com/containerd/imgcrypt/security/advisories/GHSA-8v99-48m9-c8pm', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24778', 'https://github.com/containerd/imgcrypt/releases/tag/v1.1.4', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZFTJR5CR5EOYDVOSBZEMLBHLJRTPJPUA/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TAHAAOOA3KZJC2I5WHCR3XVBJBNWTWUE/', 'https://github.com/containerd/imgcrypt/commit/6fdd9818a4d8142107b7ecd767d839c9707700d9'}
null
{'https://github.com/containerd/imgcrypt/commit/6fdd9818a4d8142107b7ecd767d839c9707700d9'}
{'https://github.com/containerd/imgcrypt/commit/6fdd9818a4d8142107b7ecd767d839c9707700d9'}
GHSA
GHSA-qm58-cvvm-c5qr
Unsafe upload filtering leading to remote code execution
### Impact Before elFinder 2.1.58, the upload filter did not disallow the upload of `.phar` files. As several Linux distributions are now shipping Apache configured in a way it will process these files as PHP scripts, attackers could gain arbitrary code execution on the server hosting the PHP connector (even in minimal configuration). ### Patches The issue has been addressed with https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1, associating `.phar` files to the right MIME type. Unless explicitly allowed in the configuration, such files cannot be uploaded anymore. This patch is part of the last release of elFinder, 2.1.58. ### Workarounds If you can't update to 2.1.58, make sure your connector is not exposed without authentication. ### Important tips Server-side scripts can often be created as text files. Currently, elFinder has an appropriate MIME type set for file extensions that are generally runnable on a web server. However, the server has various settings. In some cases, the executable file may be judged as "text/plain". Therefore, elFinder installers should understand the extensions that can be executed on the web server where elFinder is installed, and check if there are any missing items in the elFinder settings. The elFinder PHP connector has an option "additionalMimeMap" that specifies the MIME type for each extension. See [#3295(comment)](https://github.com/Studio-42/elFinder/issues/3295#issuecomment-853042139) for more information. ### References - https://snyk.io/vuln/composer:studio-42%2Felfinder - https://github.com/Studio-42/elFinder/issues/3295 - Further technical details will be disclosed on https://blog.sonarsource.com/tag/security after some time. ### For more information If you have any questions or comments about this advisory, you can contact: - The original reporters, by sending an email to support [at] snyk.io or vulnerability.research [at] sonarsource.com; - The maintainers, by opening an issue on this repository.
{'CVE-2021-23394'}
2022-04-19T19:02:59Z
2021-06-15T15:51:02Z
HIGH
8.1
{'CWE-434'}
{'https://github.com/advisories/GHSA-qm58-cvvm-c5qr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23394', 'https://snyk.io/vuln/SNYK-PHP-STUDIO42ELFINDER-1290554', 'https://github.com/Studio-42/elFinder/security/advisories/GHSA-qm58-cvvm-c5qr', 'https://github.com/Studio-42/elFinder/issues/3295', 'https://github.com/Studio-42/elFinder', 'https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1'}
null
{'https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1'}
{'https://github.com/Studio-42/elFinder/commit/75ea92decc16a5daf7f618f85dc621d1b534b5e1'}
GHSA
GHSA-4xcv-9jjx-gfj3
Denial of Service in mem
Versions of `mem` prior to 4.0.0 are vulnerable to Denial of Service (DoS). The package fails to remove old values from the cache even after a value passes its `maxAge` property. This may allow attackers to exhaust the system's memory if they are able to abuse the application logging. ## Recommendation Upgrade to version 4.0.0 or later.
null
2021-08-17T15:44:45Z
2019-07-05T21:07:58Z
MODERATE
5.1
{'CWE-400'}
{'https://github.com/advisories/GHSA-4xcv-9jjx-gfj3', 'https://bugzilla.redhat.com/show_bug.cgi?id=1623744', 'https://snyk.io/vuln/npm:mem:20180117', 'https://www.npmjs.com/advisories/1084', 'https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b'}
null
{'https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b'}
{'https://github.com/sindresorhus/mem/commit/da4e4398cb27b602de3bd55f746efa9b4a31702b'}
GHSA
GHSA-qvrv-2x7x-78x2
Reflected XSS in SilverStripe
SilverStripe through 4.4.x before 4.4.5 and 4.5.x before 4.5.2 allows Reflected XSS on the login form and custom forms. Silverstripe Forms allow malicious HTML or JavaScript to be inserted through non-scalar FormField attributes, which allows performing XSS (Cross-Site Scripting) on some forms built with user input (Request data). This can lead to phishing attempts to obtain a user&amp;#39;s credentials or other sensitive user input.
{'CVE-2019-19325'}
2021-08-19T17:22:37Z
2020-02-24T17:33:31Z
MODERATE
6.1
{'CWE-78'}
{'https://nvd.nist.gov/vuln/detail/CVE-2019-19325', 'https://github.com/advisories/GHSA-qvrv-2x7x-78x2', 'https://www.silverstripe.org/download/security-releases/cve-2019-19325', 'https://github.com/silverstripe/silverstripe-framework/commit/49fda52b12ba59f0a04bcabf78425586a8779e89'}
null
{'https://github.com/silverstripe/silverstripe-framework/commit/49fda52b12ba59f0a04bcabf78425586a8779e89'}
{'https://github.com/silverstripe/silverstripe-framework/commit/49fda52b12ba59f0a04bcabf78425586a8779e89'}
GHSA
GHSA-c6fh-56w7-fvjw
Integer overflow in Tensorflow
### Impact The [implementation of shape inference for `Dequantize`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/ops/array_ops.cc#L3001-L3034) is vulnerable to an integer overflow weakness: ```python import tensorflow as tf input = tf.constant([1,1],dtype=tf.qint32) @tf.function def test(): y = tf.raw_ops.Dequantize( input=input, min_range=[1.0], max_range=[10.0], mode='MIN_COMBINED', narrow_range=False, axis=2**31-1, dtype=tf.bfloat16) return y test() ``` The `axis` argument can be `-1` (the default value for the optional argument) or any other positive value at most the number of dimensions of the input. Unfortunately, the upper bound is not checked, and, since the code computes `axis + 1`, an attacker can trigger an integer overflow: ```cc int axis = -1; Status s = c->GetAttr("axis", &axis); // ... if (axis < -1) { return errors::InvalidArgument("axis should be at least -1, got ", axis); } // ... if (axis != -1) { ShapeHandle input; TF_RETURN_IF_ERROR(c->WithRankAtLeast(c->input(0), axis + 1, &input)); // ... } ``` ### Patches We have patched the issue in GitHub commit [b64638ec5ccaa77b7c1eb90958e3d85ce381f91b](https://github.com/tensorflow/tensorflow/commit/b64638ec5ccaa77b7c1eb90958e3d85ce381f91b). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Yu Tian of Qihoo 360 AIVul Team.
{'CVE-2022-21727'}
2022-02-10T00:16:34Z
2022-02-09T18:29:13Z
HIGH
7.6
{'CWE-190'}
{'https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/ops/array_ops.cc#L3001-L3034', 'https://github.com/advisories/GHSA-c6fh-56w7-fvjw', 'https://nvd.nist.gov/vuln/detail/CVE-2022-21727', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c6fh-56w7-fvjw', 'https://github.com/tensorflow/tensorflow/commit/b64638ec5ccaa77b7c1eb90958e3d85ce381f91b'}
null
{'https://github.com/tensorflow/tensorflow/commit/b64638ec5ccaa77b7c1eb90958e3d85ce381f91b'}
{'https://github.com/tensorflow/tensorflow/commit/b64638ec5ccaa77b7c1eb90958e3d85ce381f91b'}
GHSA
GHSA-grh7-935j-hg6w
Cross-site Scripting in Sidekiq
Sidekiq through 5.1.3 and 6.x through 6.2.0 allows XSS via the queue name of the live-poll feature when Internet Explorer is used.
{'CVE-2021-30151'}
2022-03-11T21:27:31Z
2021-10-06T17:47:17Z
MODERATE
6.1
{'CWE-79'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-30151', 'https://github.com/advisories/GHSA-grh7-935j-hg6w', 'https://lists.debian.org/debian-lts-announce/2022/03/msg00015.html', 'https://github.com/mperham/sidekiq/issues/4852', 'https://github.com/mperham/sidekiq/commit/64f70339d1dcf50a55c00d36bfdb61d97ec63ed8'}
null
{'https://github.com/mperham/sidekiq/commit/64f70339d1dcf50a55c00d36bfdb61d97ec63ed8'}
{'https://github.com/mperham/sidekiq/commit/64f70339d1dcf50a55c00d36bfdb61d97ec63ed8'}
GHSA
GHSA-29gp-2c3m-3j6m
Sandbox Escape by math function in smarty
### Impact Template authors could run arbitrary PHP code by crafting a malicious math string. If a math string is passed through as user provided data to the math function, external users could run arbitrary PHP code by crafting a malicious math string. ### Patches Please upgrade to 4.0.2 or 3.1.42 or higher. ### References See [documentation on Math function](https://www.smarty.net/docs/en/language.function.math.tpl). ### For more information If you have any questions or comments about this advisory please open an issue in [the Smarty repo](https://github.com/smarty-php/smarty)
{'CVE-2021-29454'}
2022-01-20T15:34:11Z
2022-01-12T22:43:00Z
HIGH
8.1
{'CWE-74'}
{'https://github.com/smarty-php/smarty/security/advisories/GHSA-29gp-2c3m-3j6m', 'https://github.com/smarty-php/smarty/releases/tag/v4.0.2', 'https://github.com/advisories/GHSA-29gp-2c3m-3j6m', 'https://www.smarty.net/docs/en/language.function.math.tpl', 'https://packagist.org/packages/smarty/smarty', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29454', 'https://github.com/smarty-php/smarty/commit/215d81a9fa3cd63d82fb3ab56ecaf97cf1e7db71', 'https://github.com/smarty-php/smarty/releases/tag/v3.1.42'}
null
{'https://github.com/smarty-php/smarty/commit/215d81a9fa3cd63d82fb3ab56ecaf97cf1e7db71'}
{'https://github.com/smarty-php/smarty/commit/215d81a9fa3cd63d82fb3ab56ecaf97cf1e7db71'}
GHSA
GHSA-9jjr-qqfp-ppwx
remote code execution via git repo provider
### Impact A remote code execution vulnerability has been identified in BinderHub, where providing BinderHub with maliciously crafted input could execute code in the BinderHub context, with the potential to egress credentials of the BinderHub deployment, including JupyterHub API tokens, kubernetes service accounts, and docker registry credentials. This may provide the ability to manipulate images and other user created pods in the deployment, with the potential to escalate to the host depending on the underlying kubernetes configuration. ### Patches Patch below, or [on GitHub](https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182.patch) ```diff From 9f4043d9dddc1174920e687773f27b7933f48ab6 Mon Sep 17 00:00:00 2001 From: Riccardo Castellotti <rcastell@cern.ch> Date: Thu, 19 Aug 2021 15:49:43 +0200 Subject: [PATCH] Explicitly separate git-ls-remote options from positional arguments --- binderhub/repoproviders.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/binderhub/repoproviders.py b/binderhub/repoproviders.py index f33347b..5d4b87c 100755 --- a/binderhub/repoproviders.py +++ b/binderhub/repoproviders.py @@ -484,7 +484,7 @@ class GitRepoProvider(RepoProvider): self.sha1_validate(self.unresolved_ref) except ValueError: # The ref is a head/tag and we resolve it using `git ls-remote` - command = ["git", "ls-remote", self.repo, self.unresolved_ref] + command = ["git", "ls-remote", "--", self.repo, self.unresolved_ref] result = subprocess.run(command, universal_newlines=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) if result.returncode: raise RuntimeError("Unable to run git ls-remote to get the `resolved_ref`: {}".format(result.stderr)) -- 2.25.1 ``` ### Workarounds Disable the git repo provider by specifying the `BinderHub.repo_providers` config, e.g.: ```python from binderhub.repoproviders import (GitHubRepoProvider, GitLabRepoProvider, GistRepoProvider, ZenodoProvider, FigshareProvider, HydroshareProvider, DataverseProvider) c.BinderHub.repo_providers = { 'gh': GitHubRepoProvider, 'gist': GistRepoProvider, 'gl': GitLabRepoProvider, 'zenodo': ZenodoProvider, 'figshare': FigshareProvider, 'hydroshare': HydroshareProvider, 'dataverse': DataverseProvider, } ``` ### References Credit: Jose Carlos Luna Duran (CERN) and Riccardo Castellotti (CERN). ### For more information If you have any questions or comments about this advisory: * Email us at [security@ipython.org](mailto:security@ipython.org)
{'CVE-2021-39159'}
2022-04-19T19:03:06Z
2021-08-30T16:16:58Z
CRITICAL
9.6
{'CWE-94'}
{'https://github.com/advisories/GHSA-9jjr-qqfp-ppwx', 'https://github.com/jupyterhub/binderhub/security/advisories/GHSA-9jjr-qqfp-ppwx', 'https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182.patch', 'https://nvd.nist.gov/vuln/detail/CVE-2021-39159'}
null
{'https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182'}
{'https://github.com/jupyterhub/binderhub/commit/195caac172690456dcdc8cc7a6ca50e05abf8182'}
GHSA
GHSA-9jq9-c2cv-pcrj
Cross-site Scripting by SVG upload in xwiki-platform
### Impact When using default XWiki configuration, it's possible for an attacker to upload an SVG containing a script executed when executing the download action on the file. ### Patches This problem has been patched so that the default configuration doesn't allow to display the SVG files in the browser. ### Workarounds This issue can be fixed without the patch by setting properly the configuration to download or display files, see: https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Attachments#HAttachmentdisplayordownload ### References https://jira.xwiki.org/browse/XWIKI-18368 ### For more information If you have any questions or comments about this advisory: * Open an issue in [Jira](http://jira.xwiki.org) * Email us at [security ML](mailto:security@xwiki.org)
{'CVE-2021-43841'}
2022-02-11T21:08:44Z
2022-02-10T22:42:48Z
MODERATE
4.1
{'CWE-79'}
{'https://github.com/advisories/GHSA-9jq9-c2cv-pcrj', 'https://github.com/xwiki/xwiki-platform/commit/5853d492b3a274db0d94d560e2a5ea988a271c62', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43841', 'https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-9jq9-c2cv-pcrj', 'https://jira.xwiki.org/browse/XWIKI-18368', 'https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Attachments#HAttachmentdisplayordownload'}
null
{'https://github.com/xwiki/xwiki-platform/commit/5853d492b3a274db0d94d560e2a5ea988a271c62'}
{'https://github.com/xwiki/xwiki-platform/commit/5853d492b3a274db0d94d560e2a5ea988a271c62'}
GHSA
GHSA-qqc5-rgcc-cjqh
Information Disclosure in go.elastic.co/apm
The Elastic APM agent for Go versions before 1.11.0 can leak sensitive HTTP header information when logging the details during an application panic. Normally, the APM agent will sanitize sensitive HTTP header details before sending the information to the APM server. During an application panic it is possible the headers will not be sanitized before being sent.
{'CVE-2021-22133'}
2021-05-18T18:34:18Z
2021-05-18T18:34:18Z
LOW
2.4
{'CWE-532'}
{'https://discuss.elastic.co/t/elastic-apm-agent-for-go-1-11-0-security-update/263252', 'https://github.com/elastic/apm-agent-go/commit/c5c7e21aa26a6def7790f74fbceed792ad47ef35', 'https://nvd.nist.gov/vuln/detail/CVE-2021-22133', 'https://github.com/advisories/GHSA-qqc5-rgcc-cjqh', 'https://github.com/elastic/apm-agent-go/compare/v1.10.0...v1.11.0'}
null
{'https://github.com/elastic/apm-agent-go/commit/c5c7e21aa26a6def7790f74fbceed792ad47ef35'}
{'https://github.com/elastic/apm-agent-go/commit/c5c7e21aa26a6def7790f74fbceed792ad47ef35'}
GHSA
GHSA-9hx2-hgq2-2g4f
Regular Expression Denial of Service (ReDoS) in Pillow
An issue was discovered in Pillow before 8.1.1. The PDF parser allows a regular expression DoS (ReDoS) attack via a crafted PDF file because of a catastrophic backtracking regex.
{'CVE-2021-25292'}
2021-12-02T17:47:59Z
2021-03-29T16:35:46Z
MODERATE
6.5
{'CWE-400'}
{'https://pillow.readthedocs.io/en/stable/releasenotes/8.1.1.html', 'https://github.com/advisories/GHSA-9hx2-hgq2-2g4f', 'https://github.com/python-pillow/Pillow/commit/3bce145966374dd39ce58a6fc0083f8d1890719c', 'https://security.gentoo.org/glsa/202107-33', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25292', 'https://github.com/python-pillow/Pillow/commit/6207b44ab1ff4a91d8ddc7579619876d0bb191a4'}
null
{'https://github.com/python-pillow/Pillow/commit/6207b44ab1ff4a91d8ddc7579619876d0bb191a4', 'https://github.com/python-pillow/Pillow/commit/3bce145966374dd39ce58a6fc0083f8d1890719c'}
{'https://github.com/python-pillow/Pillow/commit/6207b44ab1ff4a91d8ddc7579619876d0bb191a4', 'https://github.com/python-pillow/Pillow/commit/3bce145966374dd39ce58a6fc0083f8d1890719c'}
GHSA
GHSA-qh9q-34h6-hcv9
Directory traversal in mkdocs
The mkdocs 1.2.2 built-in dev-server allows directory traversal using the port 8000, enabling remote exploitation to obtain :sensitive information.
{'CVE-2021-40978'}
2021-11-15T15:04:24Z
2021-10-12T18:48:24Z
HIGH
7.5
{'CWE-12', 'CWE-22'}
{'https://github.com/mkdocs/mkdocs/pull/2604/commits/cddc453c9d49298e60e7d56fb71130c151cbcbe5', 'https://github.com/mkdocs/mkdocs', 'https://nvd.nist.gov/vuln/detail/CVE-2021-40978', 'https://github.com/nisdn/CVE-2021-40978/issues/1', 'https://github.com/mkdocs/mkdocs/releases/tag/1.2.3', 'https://github.com/nisdn/CVE-2021-40978', 'https://github.com/advisories/GHSA-qh9q-34h6-hcv9', 'https://github.com/mkdocs/mkdocs/issues/2601', 'https://github.com/mkdocs/mkdocs/pull/2604'}
null
{'https://github.com/mkdocs/mkdocs/pull/2604/commits/cddc453c9d49298e60e7d56fb71130c151cbcbe5'}
{'https://github.com/mkdocs/mkdocs/pull/2604/commits/cddc453c9d49298e60e7d56fb71130c151cbcbe5'}
GHSA
GHSA-fqx8-v33p-4qcc
Cross-site Scripting in enshrined/svg-sanitize
### Impact SVG sanitizer library before version `0.15.0` did not remove HTML elements wrapped in a CDATA section. As a result, SVG content embedded in HTML (fetched as `text/html`) was susceptible to cross-site scripting. Plain SVG files (fetched as `image/svg+xml`) were not affected. ### Patches This issue is fixed in `0.15.0` and higher. ### Workarounds There is currently no workaround available without upgrading. ### For more information If you have any questions or comments about this advisory: * Open an issue in [Github](https://github.com/darylldoyle/svg-sanitizer/issues) * Email us at [daryll@enshrined.co.uk](mailto:daryll@enshrined.co.uk)
{'CVE-2022-23638'}
2022-05-09T22:10:34Z
2022-02-14T22:54:18Z
MODERATE
6.2
{'CWE-79'}
{'https://github.com/darylldoyle/svg-sanitizer/issues/71', 'https://github.com/darylldoyle/svg-sanitizer/security/advisories/GHSA-fqx8-v33p-4qcc', 'https://github.com/advisories/GHSA-fqx8-v33p-4qcc', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23638', 'https://github.com/darylldoyle/svg-sanitizer/commit/17e12ba9c2881caa6b167d0fbea555c11207fbb0'}
null
{'https://github.com/darylldoyle/svg-sanitizer/commit/17e12ba9c2881caa6b167d0fbea555c11207fbb0'}
{'https://github.com/darylldoyle/svg-sanitizer/commit/17e12ba9c2881caa6b167d0fbea555c11207fbb0'}
GHSA
GHSA-333x-9vgq-v2j4
Directory Traversal in geddy
Versions 13.0.8 and earlier of geddy are vulnerable to a directory traversal attack via URI encoded attack vectors. ### Proof of Concept ``` http://localhost:4000/..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2f..%2fetc/passwd ``` ## Recommendation Update geddy to version >= 13.0.8
{'CVE-2015-5688'}
2021-08-31T20:33:52Z
2017-10-24T18:33:36Z
HIGH
0
{'CWE-22'}
{'https://nvd.nist.gov/vuln/detail/CVE-2015-5688', 'https://www.npmjs.com/advisories/10', 'https://github.com/geddy/geddy/pull/699', 'https://github.com/geddy/geddy/issues/697', 'https://nodesecurity.io/advisories/geddy-directory-traversal', 'https://github.com/geddy/geddy/commit/2de63b68b3aa6c08848f261ace550a37959ef231', 'https://github.com/geddy/geddy/releases/tag/v13.0.8', 'https://github.com/advisories/GHSA-333x-9vgq-v2j4'}
null
{'https://github.com/geddy/geddy/commit/2de63b68b3aa6c08848f261ace550a37959ef231'}
{'https://github.com/geddy/geddy/commit/2de63b68b3aa6c08848f261ace550a37959ef231'}
GHSA
GHSA-32x6-qvw6-mxj4
Forwarding of confidentials headers to third parties in fluture-node
### Impact Using `followRedirects` or `followRedirectsWith` with any of the redirection strategies built into fluture-node 4.0.0 or 4.0.1, paired with a request that includes confidential headers such as Authorization or Cookie, exposes you to a vulnerability where, if the destination server were to redirect the request to a server on a third-party domain, or the same domain over unencrypted HTTP, the headers would be included in the follow-up request and be exposed to the third party, or potential http traffic sniffing. ### Patches The redirection strategies made available in version 4.0.2 automatically redact confidential headers when a redirect is followed across to another origin. ### Workarounds Use a custom redirection strategy via the `followRedirectsWith` function. The custom strategy can be based on the new strategies available in fluture-node@4.0.2. ### References - This vulnerability was discovered after the announcement of similar vulnerabilities in the `follow-redirects` package. There is more information there: https://github.com/advisories/GHSA-74fj-2j2h-c42q and https://huntr.dev/bounties/7cf2bf90-52da-4d59-8028-a73b132de0db/ - Fixed in 125e4474f910c1507f8ec3232848626fbc0f55c4 and 0c99bc511533d48be17dc6bfe641f7d0aeb34d77
{'CVE-2022-24719'}
2022-03-15T18:05:24Z
2022-03-01T22:14:57Z
LOW
2.6
{'CWE-200', 'CWE-359', 'CWE-601'}
{'https://github.com/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4', 'https://github.com/psf/requests/pull/4718', 'https://github.com/advisories/GHSA-32x6-qvw6-mxj4', 'https://github.com/fluture-js/fluture-node/security/advisories/GHSA-32x6-qvw6-mxj4', 'https://github.com/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24719'}
null
{'https://github.com/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77', 'https://github.com/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4'}
{'https://github.com/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4', 'https://github.com/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77'}
GHSA
GHSA-6chw-6frg-f759
Regular Expression Denial of Service in Acorn
Affected versions of acorn are vulnerable to Regular Expression Denial of Service. A regex in the form of /[x-\ud800]/u causes the parser to enter an infinite loop. The string is not valid UTF16 which usually results in it being sanitized before reaching the parser. If an application processes untrusted input and passes it directly to acorn, attackers may leverage the vulnerability leading to Denial of Service.
null
2021-08-23T15:10:33Z
2020-04-03T21:48:38Z
HIGH
7.5
{'CWE-400'}
{'https://github.com/advisories/GHSA-6chw-6frg-f759', 'https://www.npmjs.com/advisories/1488', 'https://github.com/acornjs/acorn/commit/793c0e569ed1158672e3a40aeed1d8518832b802', 'https://github.com/acornjs/acorn/issues/929', 'https://snyk.io/vuln/SNYK-JS-ACORN-559469'}
null
{'https://github.com/acornjs/acorn/commit/793c0e569ed1158672e3a40aeed1d8518832b802'}
{'https://github.com/acornjs/acorn/commit/793c0e569ed1158672e3a40aeed1d8518832b802'}
GHSA
GHSA-gv3v-92v6-m48j
Improper Neutralization of CRLF Sequences in HTTP Headers in Jooby ('HTTP Response Splitting)
### Impact - Cross Site Scripting - Cache Poisoning - Page Hijacking ### Patches This was fixed in version `2.2.1`. ### Workarounds If you are unable to update, ensure that user supplied data isn't able to flow to HTTP headers. If it does, pre-sanitize for CRLF characters. ### References ##### [CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')](https://cwe.mitre.org/data/definitions/113.html) I've been poking at libraries to see if they are vulnerable to HTTP Response Splitting and Jooby is my third case of finding this vulnerability. ### Root Cause This roots cause back to this line in the Jooby codebase: https://github.com/jooby-project/jooby/blob/93cfc80aa20c188f71a442ea7a1827da380e1c27/modules/jooby-netty/src/main/java/io/jooby/internal/netty/NettyContext.java#L102 The `DefaultHttpHeaders` takes a parameter `validate` which, when `true` (as it is for the no-arg constructor) validates that the header isn't being abused to do HTTP Response Splitting. ### Reported By This vulnerability was reported by @JLLeitschuh ([Twitter](https://twitter.com/JLLeitschuh)) ### For more information If you have any questions or comments about this advisory: * Open an issue in [jooby-project/jooby](https://github.com/jooby-project/jooby/issues)
{'CVE-2020-7622'}
2022-04-19T19:02:27Z
2020-04-03T15:23:30Z
CRITICAL
9.8
{'CWE-444'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-7622', 'https://github.com/advisories/GHSA-gv3v-92v6-m48j', 'https://github.com/jooby-project/jooby/commit/b66e3342cf95205324023cfdf2cb5811e8a6dcf4', 'https://snyk.io/vuln/SNYK-JAVA-IOJOOBY-564249', 'https://github.com/jooby-project/jooby/security/advisories/GHSA-gv3v-92v6-m48j'}
null
{'https://github.com/jooby-project/jooby/commit/b66e3342cf95205324023cfdf2cb5811e8a6dcf4'}
{'https://github.com/jooby-project/jooby/commit/b66e3342cf95205324023cfdf2cb5811e8a6dcf4'}
GHSA
GHSA-fp4w-jxhp-m23p
Dependency Confusion in Bundler
Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.17 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another private gem that is explicitly depended on by the application.
{'CVE-2020-36327'}
2022-04-07T15:49:53Z
2021-05-24T18:12:33Z
HIGH
8.8
null
{'https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#2218-may-25-2021', 'https://github.com/rubygems/rubygems/issues/3982', 'https://www.zofrex.com/blog/2021/04/29/bundler-still-vulnerable-dependency-confusion-cve-2020-36327/', 'https://github.com/rubysec/ruby-advisory-db/blob/master/gems/bundler/CVE-2020-36327.yml', 'https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105', 'https://nvd.nist.gov/vuln/detail/CVE-2020-36327', 'https://github.com/rubygems/rubygems/commit/078bf682ac40017b309b5fc69f283ff640e7c129', 'https://bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html', 'https://mensfeld.pl/2021/02/rubygems-dependency-confusion-attack-side-of-things/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MWXHK5UUHVSHF7HTHMX6JY3WXDVNIHSL/', 'https://github.com/rubygems/rubygems/pull/4609', 'https://github.com/advisories/GHSA-fp4w-jxhp-m23p'}
null
{'https://github.com/rubygems/rubygems/commit/078bf682ac40017b309b5fc69f283ff640e7c129'}
{'https://github.com/rubygems/rubygems/commit/078bf682ac40017b309b5fc69f283ff640e7c129'}
GHSA
GHSA-mgh8-hcwj-h57v
Improper Restriction of XML External Entity Reference in Apache Olingo
The XML content type entity deserializer in Apache Olingo versions 4.0.0 to 4.6.0 is not configured to deny the resolution of external entities. Request with content type "application/xml", which trigger the deserialization of entities, can be used to trigger XXE attacks.
{'CVE-2019-17554'}
2021-08-19T16:53:27Z
2020-02-04T22:37:43Z
MODERATE
5.5
{'CWE-611'}
{'https://lists.apache.org/thread.html/r6d03e45b81eab03580cf7f8bb51cb3e9a1b10a2cc0c6a2d3cc92ed0c@%3Cannounce.apache.org%3E', 'https://seclists.org/bugtraq/2019/Dec/11', 'https://github.com/apache/olingo-odata4/commit/5948974ad28271818e2afe747c71cde56a7f2c63', 'https://issues.apache.org/jira/browse/OLINGO-1409', 'https://github.com/advisories/GHSA-mgh8-hcwj-h57v', 'https://nvd.nist.gov/vuln/detail/CVE-2019-17554', 'https://mail-archives.apache.org/mod_mbox/olingo-user/201912.mbox/%3CCAGSZ4d7Ty%3DL-n_iAzT6vcQp65BY29XZDS5tMoM8MdDrb1moM7A%40mail.gmail.com%3E', 'https://github.com/apache/olingo-odata4/commit/c3f982db3d97e395d313ae8f231202bb2139882c', 'http://packetstormsecurity.com/files/155619/Apache-Olingo-OData-4.6.x-XML-Injection.html'}
null
{'https://github.com/apache/olingo-odata4/commit/c3f982db3d97e395d313ae8f231202bb2139882c', 'https://github.com/apache/olingo-odata4/commit/5948974ad28271818e2afe747c71cde56a7f2c63'}
{'https://github.com/apache/olingo-odata4/commit/5948974ad28271818e2afe747c71cde56a7f2c63', 'https://github.com/apache/olingo-odata4/commit/c3f982db3d97e395d313ae8f231202bb2139882c'}
GHSA
GHSA-qh32-6jjc-qprm
Null pointer dereference in tensorflow-lite
### Impact A crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L1224-L1227 However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. ### Patches We have patched the issue in 0b5662bc and will release patch releases for all versions between 1.15 and 2.3. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by members of the Aivul Team from Qihoo 360 but was also discovered through variant analysis of [GHSA-cvpc-8phh-8f45](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cvpc-8phh-8f45).
{'CVE-2020-15209'}
2021-08-26T15:19:20Z
2020-09-25T18:28:46Z
MODERATE
5.9
{'CWE-476'}
{'https://github.com/tensorflow/tensorflow/commit/0b5662bc2be13a8c8f044d925d87fb6e56247cd8', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-qh32-6jjc-qprm', 'http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html', 'https://github.com/advisories/GHSA-qh32-6jjc-qprm', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15209', 'https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1'}
null
{'https://github.com/tensorflow/tensorflow/commit/0b5662bc2be13a8c8f044d925d87fb6e56247cd8'}
{'https://github.com/tensorflow/tensorflow/commit/0b5662bc2be13a8c8f044d925d87fb6e56247cd8'}
GHSA
GHSA-3qh4-r86r-grvm
Arbitrary JavaScript Execution in typed-function
Versions of `typed-function` prior to 0.10.6 are vulnerable to Arbitrary JavaScript Execution. Function names are not properly sanitized and may allow an attacker to execute arbitrary code. ## Recommendation Upgrade to version 0.10.6 or later.
{'CVE-2017-1001004'}
2021-01-07T23:31:27Z
2020-09-02T18:24:39Z
HIGH
0
{'CWE-94'}
{'https://github.com/josdejong/typed-function/commit/6478ef4f2c3f3c2d9f2c820e2db4b4ba3425e6fe?diff=split#diff-9e1f22c2954a38db1fdf444dbc74e0a8', 'https://github.com/advisories/GHSA-3qh4-r86r-grvm', 'https://github.com/josdejong/typed-function/commit/6478ef4f2c3f3c2d9f2c820e2db4b4ba3425e6fe', 'https://github.com/josdejong/typed-function/blob/master/HISTORY.md#2017-11-18-version-0106', 'https://snyk.io/vuln/SNYK-JS-TYPEDFUNCTION-174139', 'https://nvd.nist.gov/vuln/detail/CVE-2017-1001004', 'https://www.npmjs.com/advisories/819'}
null
{'https://github.com/josdejong/typed-function/commit/6478ef4f2c3f3c2d9f2c820e2db4b4ba3425e6fe?diff=split#diff-9e1f22c2954a38db1fdf444dbc74e0a8', 'https://github.com/josdejong/typed-function/commit/6478ef4f2c3f3c2d9f2c820e2db4b4ba3425e6fe'}
{'https://github.com/josdejong/typed-function/commit/6478ef4f2c3f3c2d9f2c820e2db4b4ba3425e6fe?diff=split#diff-9e1f22c2954a38db1fdf444dbc74e0a8', 'https://github.com/josdejong/typed-function/commit/6478ef4f2c3f3c2d9f2c820e2db4b4ba3425e6fe'}
GHSA
GHSA-3r7g-wrpr-j5g4
Improper Authentication in django-mfa3
### Impact django-mfa3 is a library that implements multi factor authentication for the django web framework. It achieves this by modifying the regular login view. Django however has a second login view for its admin area. This second login view was not modified, so the multi factor authentication can be bypassed. You are affected if you have activated both django-mfa3 (< 0.5.0) and django.contrib.admin and have not taken any other measures to prevent users from accessing the admin login view. ### Patches The issue has been fixed in django-mfa3 0.5.0. ### Workarounds It is possible to work around the issue by overwriting the admin login route, e.g. by adding the following URL definition *before* the admin routes: url('admin/login/', lambda request: redirect(settings.LOGIN_URL) ### References - [django-mfa3 changelog](https://github.com/xi/django-mfa3/blob/main/CHANGES.md#050-2022-04-15)
{'CVE-2022-24857'}
2022-04-22T20:48:29Z
2022-04-22T20:48:28Z
HIGH
7.3
{'CWE-287'}
{'https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de', 'https://github.com/xi/django-mfa3/blob/main/CHANGES.md#050-2022-04-15', 'https://github.com/advisories/GHSA-3r7g-wrpr-j5g4', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24857', 'https://github.com/xi/django-mfa3/security/advisories/GHSA-3r7g-wrpr-j5g4'}
null
{'https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de'}
{'https://github.com/xi/django-mfa3/commit/32f656e22df120b84bdf010e014bb19bd97971de'}
GHSA
GHSA-gx8x-g87m-h5q6
Denial of Service (DoS) in Nokogiri on JRuby
## Summary Nokogiri `v1.13.4` updates the vendored `org.cyberneko.html` library to `1.9.22.noko2` which addresses [CVE-2022-24839](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv). That CVE is rated 7.5 (High Severity). See [GHSA-9849-p7jc-9rmv](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv) for more information. Please note that this advisory only applies to the **JRuby** implementation of Nokogiri `< 1.13.4`. ## Mitigation Upgrade to Nokogiri `>= 1.13.4`. ## Impact ### [CVE-2022-24839](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv) in nekohtml - **Severity**: High 7.5 - **Type**: [CWE-400](https://cwe.mitre.org/data/definitions/400.html) Uncontrolled Resource Consumption - **Description**: The fork of `org.cyberneko.html` used by Nokogiri (Rubygem) raises a `java.lang.OutOfMemoryError` exception when parsing ill-formed HTML markup. - **See also**: [GHSA-9849-p7jc-9rmv](https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv)
null
2022-04-11T21:38:21Z
2022-04-11T21:38:11Z
HIGH
7.5
{'CWE-400'}
{'https://github.com/sparklemotion/nekohtml/commit/a800fce3b079def130ed42a408ff1d09f89e773d', 'https://github.com/sparklemotion/nekohtml/security/advisories/GHSA-9849-p7jc-9rmv', 'https://github.com/advisories/GHSA-gx8x-g87m-h5q6', 'https://groups.google.com/g/ruby-security-ann/c/vX7qSjsvWis/m/TJWN4oOKBwAJ?utm_medium=email&utm_source=footer', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24839', 'https://github.com/sparklemotion/nokogiri/releases/tag/v1.13.4', 'https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-gx8x-g87m-h5q6'}
null
{'https://github.com/sparklemotion/nekohtml/commit/a800fce3b079def130ed42a408ff1d09f89e773d'}
{'https://github.com/sparklemotion/nekohtml/commit/a800fce3b079def130ed42a408ff1d09f89e773d'}
GHSA
GHSA-vrcf-g539-x6h3
Uncontrolled deserialization of a pickled object in rediswrapper allows attackers to execute arbitrary scripts
Uncontrolled deserialization of a pickled object in models.py in Frost Ming rediswrapper (aka Redis Wrapper) before 0.3.0 allows attackers to execute arbitrary scripts.
{'CVE-2019-17206'}
2022-03-23T20:24:50Z
2019-11-20T01:37:13Z
CRITICAL
9.8
{'CWE-502'}
{'https://nvd.nist.gov/vuln/detail/CVE-2019-17206', 'https://github.com/frostming/rediswrapper/commit/748f60bafd857c24f65683426f665350e2c3f91b', 'https://github.com/frostming/rediswrapper/pull/1', 'https://github.com/frostming/rediswrapper/compare/v0.2.1...v0.3.0', 'https://github.com/advisories/GHSA-vrcf-g539-x6h3', 'https://github.com/frostming/rediswrapper/releases/tag/v0.3.0'}
null
{'https://github.com/frostming/rediswrapper/commit/748f60bafd857c24f65683426f665350e2c3f91b'}
{'https://github.com/frostming/rediswrapper/commit/748f60bafd857c24f65683426f665350e2c3f91b'}
GHSA
GHSA-59g4-hpg3-3gcp
Files Accessible to External Parties in Opencast
Opencast before version 10.6 allows references to local file URLs in ingested media packages, allowing attackers to include local files from Opencast's host machines and making them available via the web interface. ### Impact Before Opencast 10.6, Opencast would [open and include local files during ingests](https://github.com/opencast/opencast/blob/69952463971cf578363e3b97d8edaf334ff51253/modules/ingest-service-impl/src/main/java/org/opencastproject/ingest/impl/IngestServiceImpl.java#L1587). Attackers could exploit this to include most local files the process has read access to, extracting secrets from the host machine. For example, to expose the `custom.properties` of develop.opencast.org via the asset manager, an attacker could have run: ``` curl -f -i -u admin:opencast \ https://develop.opencast.org/ingest/addMediaPackage/fast \ -F 'flavor=presenter/source'\ -F mediaUri=file:///srv/opencast/opencast-dist-allinone/etc/custom.properties\ -F title="custom.properties" ``` An attacker would need to have the privileges required to add new media to exploit this. But these are often widely given. ### Patches The issue has been fixed in Opencast 10.6 and 11.0. ### Workarounds You can mitigate this issue by narrowing down the read access Opencast has to files on the file system using UNIX permissions or mandatory access control systems like SELinux. This cannot prevent access to files Opencast needs to read though and we highly recommend updating. ### References - [Example of problematic code](https://github.com/opencast/opencast/blob/69952463971cf578363e3b97d8edaf334ff51253/modules/ingest-service-impl/src/main/java/org/opencastproject/ingest/impl/IngestServiceImpl.java#L1587). - [Patch fixing the issue](https://github.com/opencast/opencast/commit/65c46b9d3e8f045c544881059923134571897764) ### For more information If you have any questions or comments about this advisory: * Open an issue in [our issue tracker](https://github.com/opencast/opencast/issues) * Email us at [security@opencast.org](mailto:security@opencast.org)
{'CVE-2021-43821'}
2022-04-19T19:03:13Z
2021-12-14T21:44:03Z
CRITICAL
9.9
{'CWE-552'}
{'https://github.com/opencast/opencast/security/advisories/GHSA-59g4-hpg3-3gcp', 'https://github.com/opencast/opencast/blob/69952463971cf578363e3b97d8edaf334ff51253/modules/ingest-service-impl/src/main/java/org/opencastproject/ingest/impl/IngestServiceImpl.java#L1587', 'https://github.com/opencast/opencast/commit/65c46b9d3e8f045c544881059923134571897764', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43821', 'https://mvnrepository.com/artifact/org.opencastproject/opencast-ingest-service-impl', 'https://github.com/advisories/GHSA-59g4-hpg3-3gcp'}
null
{'https://github.com/opencast/opencast/commit/65c46b9d3e8f045c544881059923134571897764'}
{'https://github.com/opencast/opencast/commit/65c46b9d3e8f045c544881059923134571897764'}
GHSA
GHSA-33rv-m2gp-mm2r
Prototype pollution in safe-flat
Prototype pollution vulnerability in 'safe-flat' versions 2.0.0 through 2.0.1 allows an attacker to cause a denial of service and may lead to remote code execution.
{'CVE-2021-25927'}
2021-06-21T17:18:29Z
2021-06-21T17:18:29Z
CRITICAL
9.8
{'CWE-1321'}
{'https://github.com/advisories/GHSA-33rv-m2gp-mm2r', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25927', 'https://github.com/jessie-codes/safe-flat/commit/4b9b7db976bba8c968354f4315f5f9c219b7cbf3', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25927'}
null
{'https://github.com/jessie-codes/safe-flat/commit/4b9b7db976bba8c968354f4315f5f9c219b7cbf3'}
{'https://github.com/jessie-codes/safe-flat/commit/4b9b7db976bba8c968354f4315f5f9c219b7cbf3'}
GHSA
GHSA-hhfg-6hfc-rvxm
Regular Expression Denial of Service in jsoneditor
JSON Editor is a web-based tool to view, edit, format, and validate JSON. It has various modes such as a tree editor, a code editor, and a plain text editor. The jsoneditor package is vulnerable to ReDoS (regular expression denial of service). An attacker that is able to provide a crafted element as input to the getInnerText function may cause an application to consume an excessive amount of CPU. Below pinned line using vulnerable regex.
{'CVE-2021-3822'}
2022-05-05T13:49:44Z
2021-09-29T17:15:55Z
MODERATE
5.3
{'CWE-400', 'CWE-697', 'CWE-1333'}
{'https://huntr.dev/bounties/1e3ed803-b7ed-42f1-a4ea-c4c75da9de73', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3822', 'https://github.com/advisories/GHSA-hhfg-6hfc-rvxm', 'https://github.com/josdejong/jsoneditor/commit/092e386cf49f2a1450625617da8e0137ed067c3e'}
null
{'https://github.com/josdejong/jsoneditor/commit/092e386cf49f2a1450625617da8e0137ed067c3e'}
{'https://github.com/josdejong/jsoneditor/commit/092e386cf49f2a1450625617da8e0137ed067c3e'}
GHSA
GHSA-p9m8-27x8-rg87
Critical vulnerability found in cron-utils
### Impact A Template Injection was identified in cron-utils enabling attackers to inject arbitrary Java EL expressions, leading to unauthenticated Remote Code Execution (RCE) vulnerability. Versions up to 9.1.2 are susceptible to this vulnerability. Please note, that only projects using the @Cron annotation to validate untrusted Cron expressions are affected. ### Patches The issue was patched and a new version was released. Please upgrade to version 9.1.6. ### Workarounds There are no known workarounds up to this moment. ### References A description of the issue is provided in [issue 461](https://github.com/jmrozanec/cron-utils/issues/461) ### For more information If you have any questions or comments about this advisory: Open an issue in the [cron-utils Github repository](https://github.com/jmrozanec/cron-utils)
{'CVE-2021-41269'}
2022-04-19T19:03:15Z
2021-11-15T23:27:11Z
CRITICAL
10
{'CWE-94'}
{'https://github.com/advisories/GHSA-p9m8-27x8-rg87', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41269', 'https://github.com/jmrozanec/cron-utils/commit/d6707503ec2f20947f79e38f861dba93b39df9da', 'https://github.com/jmrozanec/cron-utils/security/advisories/GHSA-p9m8-27x8-rg87', 'https://github.com/jmrozanec/cron-utils/commit/cfd2880f80e62ea74b92fa83474c2aabdb9899da', 'https://github.com/jmrozanec/cron-utils/issues/461'}
null
{'https://github.com/jmrozanec/cron-utils/commit/cfd2880f80e62ea74b92fa83474c2aabdb9899da', 'https://github.com/jmrozanec/cron-utils/commit/d6707503ec2f20947f79e38f861dba93b39df9da'}
{'https://github.com/jmrozanec/cron-utils/commit/d6707503ec2f20947f79e38f861dba93b39df9da', 'https://github.com/jmrozanec/cron-utils/commit/cfd2880f80e62ea74b92fa83474c2aabdb9899da'}
GHSA
GHSA-gjwp-7v3g-99pj
Cross-site Request Forgery (CSRF) in joplin
The package joplin before 2.3.2 are vulnerable to Cross-site Request Forgery (CSRF) due to missing CSRF checks in various forms.
{'CVE-2021-23431'}
2021-09-02T17:09:05Z
2021-09-02T17:09:05Z
MODERATE
5.4
{'CWE-352'}
{'https://github.com/laurent22/joplin/commit/19b45de2981c09f6f387498ef96d32b4811eba5e', 'https://github.com/advisories/GHSA-gjwp-7v3g-99pj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-23431', 'https://snyk.io/vuln/SNYK-JS-JOPLIN-1325537'}
null
{'https://github.com/laurent22/joplin/commit/19b45de2981c09f6f387498ef96d32b4811eba5e'}
{'https://github.com/laurent22/joplin/commit/19b45de2981c09f6f387498ef96d32b4811eba5e'}
GHSA
GHSA-5qjq-69w6-fg57
XSS vulnerability with translator
Flarum's translation system allowed for string inputs to be converted into HTML DOM nodes when rendered. This change was made after v0.1.0-beta.16 (our last beta before v1.0.0) and was not noticed or documented. This allowed for any user to type malicious HTML markup within certain user input fields and have this execute on client browsers. The example which led to the discovery of this vulnerability was in the forum search box. Entering faux-malicious HTML markup, such as <script>alert('test')</script> resulted in an alert box appearing on the forum. This attack could also be modified to perform AJAX requests on behalf of a user, possibly deleting discussions, modifying their settings or profile, or even modifying settings on the Admin panel if the attack was targetted towards a privileged user. ### Impact All Flarum communities that run flarum v1.0.0 or v1.0.1 are impacted. ### Patches The vulnerability has been fixed and published as flarum/core v1.0.2. All communities running Flarum v1.0 have to upgrade as soon as possible to v1.0.2 using: ``` composer update --prefer-dist --no-dev -a -W ``` You can then confirm you run the latest version using: ``` composer show flarum/core ``` ### Workarounds __None.__ ### For more information For any questions or comments on this vulnerability please visit https://discuss.flarum.org/d/27558. For support questions create a discussion at https://discuss.flarum.org/t/support. A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly.
{'CVE-2021-32671'}
2022-04-19T19:02:59Z
2021-06-07T21:48:17Z
CRITICAL
10
{'CWE-79'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-32671', 'https://github.com/flarum/core/commit/440bed81b8019dff00642c8f493b4909d505a28a', 'https://github.com/flarum/core/security/advisories/GHSA-5qjq-69w6-fg57', 'https://github.com/advisories/GHSA-5qjq-69w6-fg57', 'https://packagist.org/packages/flarum/core'}
null
{'https://github.com/flarum/core/commit/440bed81b8019dff00642c8f493b4909d505a28a'}
{'https://github.com/flarum/core/commit/440bed81b8019dff00642c8f493b4909d505a28a'}
GHSA
GHSA-4r62-v4vq-hr96
Regular Expression Denial of Service (REDoS) in Marked
### Impact _What kind of vulnerability is it? Who is impacted?_ [Regular expression Denial of Service](https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS) A Denial of Service attack can affect anyone who runs user generated code through `marked`. ### Patches _Has the problem been patched? What versions should users upgrade to?_ patched in v2.0.0 ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ None. ### References _Are there any links users can visit to find out more?_ https://github.com/markedjs/marked/issues/1927 https://owasp.org/www-community/attacks/Regular_expression_Denial_of_Service_-_ReDoS ### For more information If you have any questions or comments about this advisory: * Open an issue in [marked](https://github.com/markedjs/marked/issues)
{'CVE-2021-21306'}
2022-04-19T19:02:46Z
2021-02-08T21:17:58Z
MODERATE
5.3
{'CWE-400'}
{'https://github.com/markedjs/marked/commit/7293251c438e3ee968970f7609f1a27f9007bccd', 'https://www.npmjs.com/package/marked', 'https://github.com/markedjs/marked/issues/1927', 'https://nvd.nist.gov/vuln/detail/CVE-2021-21306', 'https://github.com/markedjs/marked/security/advisories/GHSA-4r62-v4vq-hr96', 'https://github.com/markedjs/marked/pull/1864', 'https://github.com/advisories/GHSA-4r62-v4vq-hr96'}
null
{'https://github.com/markedjs/marked/commit/7293251c438e3ee968970f7609f1a27f9007bccd'}
{'https://github.com/markedjs/marked/commit/7293251c438e3ee968970f7609f1a27f9007bccd'}
GHSA
GHSA-4p55-xj37-fx7g
Improper Authorization in Strapi
In Strapi before 3.2.5, there is no admin::hasPermissions restriction for CTB (aka content-type-builder) routes.
{'CVE-2020-27665'}
2021-01-08T21:21:57Z
2020-10-29T18:29:31Z
MODERATE
0
{'CWE-276'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-27665', 'https://github.com/strapi/strapi/releases/tag/v3.2.5', 'https://snyk.io/vuln/SNYK-JS-STRAPIPLUGINCONTENTTYPEBUILDER-1021616', 'https://github.com/strapi/strapi/commit/3cdd73987950d5c7976701047b38203e902007bb', 'https://github.com/strapi/strapi/pull/8439', 'https://github.com/advisories/GHSA-4p55-xj37-fx7g'}
null
{'https://github.com/strapi/strapi/commit/3cdd73987950d5c7976701047b38203e902007bb'}
{'https://github.com/strapi/strapi/commit/3cdd73987950d5c7976701047b38203e902007bb'}
GHSA
GHSA-6c3j-c64m-qhgq
XSS in jQuery as used in Drupal, Backdrop CMS, and other products
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
{'CVE-2019-11358'}
2022-04-07T15:12:22Z
2019-04-26T16:29:11Z
MODERATE
6.1
{'CWE-79', 'CWE-1321'}
{'https://seclists.org/bugtraq/2019/Apr/32', 'https://lists.debian.org/debian-lts-announce/2019/05/msg00029.html', 'https://access.redhat.com/errata/RHSA-2019:3023', 'https://lists.apache.org/thread.html/f9bc3e55f4e28d1dcd1a69aae6d53e609a758e34d2869b4d798e13cc@%3Cissues.drill.apache.org%3E', 'https://lists.apache.org/thread.html/rac25da84ecdcd36f6de5ad0d255f4e967209bbbebddb285e231da37d@%3Cissues.flink.apache.org%3E', 'https://backdropcms.org/security/backdrop-sa-core-2019-009', 'https://nvd.nist.gov/vuln/detail/CVE-2019-11358', 'https://www.debian.org/security/2019/dsa-4460', 'http://packetstormsecurity.com/files/153237/RetireJS-CORS-Issue-Script-Execution.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WZW27UCJ5CYFL4KFFFMYMIBNMIU2ALG5/', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://github.com/jquery/jquery/commit/753d591aea698e57d6db58c9f722cd0808619b1b', 'https://lists.apache.org/thread.html/r7d64895cc4dff84d0becfc572b20c0e4bf9bfa7b10c6f5f73e783734@%3Cdev.storm.apache.org%3E', 'https://lists.apache.org/thread.html/r2baacab6e0acb5a2092eb46ae04fd6c3e8277b4fd79b1ffb7f3254fa@%3Cissues.flink.apache.org%3E', 'https://lists.apache.org/thread.html/b736d0784cf02f5a30fbb4c5902762a15ad6d47e17e2c5a17b7d6205@%3Ccommits.airflow.apache.org%3E', 'http://seclists.org/fulldisclosure/2019/May/11', 'https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00025.html', 'http://packetstormsecurity.com/files/152787/dotCMS-5.1.1-Vulnerable-Dependencies.html', 'https://github.com/advisories/GHSA-6c3j-c64m-qhgq', 'https://www.debian.org/security/2019/dsa-4434', 'https://seclists.org/bugtraq/2019/Jun/12', 'https://lists.apache.org/thread.html/6097cdbd6f0a337bedd9bb5cc441b2d525ff002a96531de367e4259f@%3Ccommits.airflow.apache.org%3E', 'http://seclists.org/fulldisclosure/2019/May/10', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/5IABSKTYZ5JUGL735UKGXL5YPRYOPUYI/', 'https://lists.apache.org/thread.html/rca37935d661f4689cb4119f1b3b224413b22be161b678e6e6ce0c69b@%3Ccommits.nifi.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RLXRX23725JL366CNZGJZ7AQQB7LHQ6F/', 'https://lists.apache.org/thread.html/5928aa293e39d248266472210c50f176cac1535220f2486e6a7fa844@%3Ccommits.airflow.apache.org%3E', 'https://lists.apache.org/thread.html/08720ef215ee7ab3386c05a1a90a7d1c852bf0706f176a7816bf65fc@%3Ccommits.airflow.apache.org%3E', 'https://www.oracle.com//security-alerts/cpujul2021.html', 'https://lists.apache.org/thread.html/r7e8ebccb7c022e41295f6fdb7b971209b83702339f872ddd8cf8bf73@%3Cissues.flink.apache.org%3E', 'https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html', 'https://lists.apache.org/thread.html/r38f0d1aa3c923c22977fe7376508f030f22e22c1379fbb155bf29766@%3Cdev.syncope.apache.org%3E', 'https://www.drupal.org/sa-core-2019-006', 'https://access.redhat.com/errata/RHSA-2019:3024', 'https://github.com/jquery/jquery/pull/4333', 'https://lists.apache.org/thread.html/88fb0362fd40e5b605ea8149f63241537b8b6fb5bfa315391fc5cbb7@%3Ccommits.airflow.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2020/02/msg00024.html', 'https://access.redhat.com/errata/RHSA-2019:1456', 'https://snyk.io/vuln/SNYK-JS-JQUERY-174006', 'http://packetstormsecurity.com/files/156743/OctoberCMS-Insecure-Dependencies.html', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://www.privacy-wise.com/mitigating-cve-2019-11358-in-old-versions-of-jquery/', 'https://www.oracle.com/security-alerts/cpujan2020.html', 'https://blog.jquery.com/2019/04/10/jquery-3-4-0-released/', 'https://lists.apache.org/thread.html/519eb0fd45642dcecd9ff74cb3e71c20a4753f7d82e2f07864b5108f@%3Cdev.drill.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QV3PKZC3PQCO3273HAT76PAQZFBEO4KP/', 'https://www.synology.com/security/advisory/Synology_SA_19_19', 'https://lists.apache.org/thread.html/r41b5bfe009c845f67d4f68948cc9419ac2d62e287804aafd72892b08@%3Cissues.flink.apache.org%3E', 'https://security.netapp.com/advisory/ntap-20190919-0001/', 'http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00006.html', 'https://lists.apache.org/thread.html/b0656d359c7d40ec9f39c8cc61bca66802ef9a2a12ee199f5b0c1442@%3Cdev.drill.apache.org%3E', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4UOAZIFCSZ3ENEFOR5IXX6NFAD3HV7FA/', 'https://access.redhat.com/errata/RHSA-2019:2587', 'https://seclists.org/bugtraq/2019/May/18', 'https://lists.apache.org/thread.html/ba79cf1658741e9f146e4c59b50aee56656ea95d841d358d006c18b6@%3Ccommits.roller.apache.org%3E', 'https://access.redhat.com/errata/RHBA-2019:1570', 'https://lists.apache.org/thread.html/bcce5a9c532b386c68dab2f6b3ce8b0cc9b950ec551766e76391caa3@%3Ccommits.nifi.apache.org%3E', 'https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44601', 'https://www.oracle.com/security-alerts/cpuoct2020.html', 'http://www.securityfocus.com/bid/108023', 'https://www.oracle.com/security-alerts/cpujan2021.html', 'https://lists.apache.org/thread.html/r2041a75d3fc09dec55adfd95d598b38d22715303f65c997c054844c9@%3Cissues.flink.apache.org%3E', 'https://lists.debian.org/debian-lts-announce/2019/05/msg00006.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KYH3OAGR2RTCHRA5NOKX2TES7SNQMWGO/', 'https://www.oracle.com/security-alerts/cpuapr2020.html', 'https://www.oracle.com/security-alerts/cpujul2020.html', 'https://lists.apache.org/thread.html/r7aac081cbddb6baa24b75e74abf0929bf309b176755a53e3ed810355@%3Cdev.flink.apache.org%3E', 'http://seclists.org/fulldisclosure/2019/May/13', 'http://www.openwall.com/lists/oss-security/2019/06/03/2', 'https://www.tenable.com/security/tns-2019-08', 'https://www.tenable.com/security/tns-2020-02'}
null
{'https://github.com/jquery/jquery/commit/753d591aea698e57d6db58c9f722cd0808619b1b'}
{'https://github.com/jquery/jquery/commit/753d591aea698e57d6db58c9f722cd0808619b1b'}
GHSA
GHSA-43jf-985q-588j
Multiple `CHECK`-fails in `function.cc` in TensowFlow
### Impact A malicious user can cause a denial of service by altering a `SavedModel` such that [assertions in `function.cc`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/function.cc) would be falsified and crash the Python interpreter. ### Patches We have patched the issue in GitHub commits [dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2](https://github.com/tensorflow/tensorflow/commit/dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2) and [3d89911481ba6ebe8c88c1c0b595412121e6c645](https://github.com/tensorflow/tensorflow/commit/3d89911481ba6ebe8c88c1c0b595412121e6c645). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.
{'CVE-2022-23586'}
2022-02-11T20:31:30Z
2022-02-09T23:27:08Z
MODERATE
6.5
{'CWE-617'}
{'https://github.com/tensorflow/tensorflow/commit/3d89911481ba6ebe8c88c1c0b595412121e6c645', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-43jf-985q-588j', 'https://github.com/tensorflow/tensorflow/commit/dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2', 'https://nvd.nist.gov/vuln/detail/CVE-2022-23586', 'https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/core/framework/function.cc', 'https://github.com/advisories/GHSA-43jf-985q-588j'}
null
{'https://github.com/tensorflow/tensorflow/commit/3d89911481ba6ebe8c88c1c0b595412121e6c645', 'https://github.com/tensorflow/tensorflow/commit/dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2'}
{'https://github.com/tensorflow/tensorflow/commit/3d89911481ba6ebe8c88c1c0b595412121e6c645', 'https://github.com/tensorflow/tensorflow/commit/dcc21c7bc972b10b6fb95c2fb0f4ab5a59680ec2'}
GHSA
GHSA-2v5f-23xc-v9qr
Cross-site scripting
The npm package ansi_up converts ANSI escape codes into HTML. In ansi_up v4, ANSI escape codes can be used to create HTML hyperlinks. Due to insufficient URL sanitization, this feature is affected by a cross-site scripting (XSS) vulnerability. This issue is fixed in v5.0.0.
{'CVE-2021-3377'}
2021-03-11T22:50:39Z
2021-03-11T22:50:39Z
MODERATE
0
{'CWE-79'}
{'https://github.com/drudru/ansi_up/commit/c8c726ed1db979bae4f257b7fa41775155ba2e27', 'https://github.com/advisories/GHSA-2v5f-23xc-v9qr', 'https://nvd.nist.gov/vuln/detail/CVE-2021-3377', 'https://doyensec.com/resources/Doyensec_Advisory_ansi_up4_XSS.pdf'}
null
{'https://github.com/drudru/ansi_up/commit/c8c726ed1db979bae4f257b7fa41775155ba2e27'}
{'https://github.com/drudru/ansi_up/commit/c8c726ed1db979bae4f257b7fa41775155ba2e27'}
GHSA
GHSA-xc6g-ggrc-qq4r
Cross-Site Scripting in sanitize-html
Affected versions of `sanitize-html` are vulnerable to cross-site scripting when allowedTags includes at least one `nonTextTag`. ## Proof of Concept ``` var sanitizeHtml = require('sanitize-html'); var dirty = '!<textarea>&lt;/textarea&gt;<svg/onload=prompt`xs`&gt;</textarea>!'; var clean = sanitizeHtml(dirty, { allowedTags: [ 'textarea' ] }); console.log(clean); // !<textarea></textarea><svg/onload=prompt`xs`></textarea>! ``` ## Recommendation Update to version 1.11.4 or later.
{'CVE-2017-16016'}
2021-01-08T21:15:03Z
2018-11-09T17:47:23Z
MODERATE
0
{'CWE-79'}
{'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403)))', 'https://nvd.nist.gov/vuln/detail/CVE-2017-16016', 'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403', 'https://nodesecurity.io/advisories/154', 'https://github.com/punkave/sanitize-html/issues/100', 'https://www.npmjs.com/advisories/154', 'https://github.com/advisories/GHSA-xc6g-ggrc-qq4r', 'https://npmjs.com/package/sanitize-html#discarding-the-entire-contents-of-a-disallowed-tag'}
null
{'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403)))', 'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403'}
{'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403', 'https://github.com/punkave/sanitize-html/commit/5d205a1005ba0df80e21d8c64a15bb3accdb2403)))'}
GHSA
GHSA-2h63-qp69-fwvw
Server-side request forgery (SSRF) in Apache Batik
Apache Batik 1.13 is vulnerable to server-side request forgery, caused by improper input validation by the NodePickerPanel. By using a specially-crafted argument, an attacker could exploit this vulnerability to cause the underlying server to make arbitrary GET requests.
{'CVE-2020-11987'}
2022-02-08T21:33:50Z
2022-01-06T20:35:54Z
HIGH
8.2
{'CWE-20', 'CWE-918'}
{'https://www.oracle.com/security-alerts/cpujan2022.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/W7EAYO5XIHD6OIEA3HPK64UDDBSLNAC5/', 'https://lists.apache.org/thread.html/r588d05a0790b40a0eb81088252e1e8c1efb99706631421f17038eb05@%3Cdev.poi.apache.org%3E', 'https://xmlgraphics.apache.org/security.html', 'https://github.com/advisories/GHSA-2h63-qp69-fwvw', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11987', 'https://github.com/apache/xmlgraphics-batik/commit/0ef5b661a1f77772d1110877ea9e0287987098f6', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JEDID4DAVPECE6O4QQCSIS75BLLBUUAM/', 'https://www.oracle.com/security-alerts/cpuoct2021.html', 'https://lists.apache.org/thread.html/r2877ae10e8be56a3c52d03e373512ddd32f16b863f24c2e22f5a5ba2@%3Cdev.poi.apache.org%3E', 'https://www.oracle.com/security-alerts/cpuApr2021.html', 'https://www.oracle.com//security-alerts/cpujul2021.html'}
null
{'https://github.com/apache/xmlgraphics-batik/commit/0ef5b661a1f77772d1110877ea9e0287987098f6'}
{'https://github.com/apache/xmlgraphics-batik/commit/0ef5b661a1f77772d1110877ea9e0287987098f6'}
GHSA
GHSA-v89p-5hr2-4rh4
Out-of-bounds write
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1131, CVE-2019-1139, CVE-2019-1140, CVE-2019-1141, CVE-2019-1195, CVE-2019-1196.
{'CVE-2019-1197'}
2021-03-29T20:56:15Z
2021-03-29T20:56:15Z
HIGH
7.5
{'CWE-787'}
{'https://github.com/chakra-core/ChakraCore/commit/bf52b6cfa96d6395046d0aaf87396cd7ca13f6cb', 'https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1197', 'https://nvd.nist.gov/vuln/detail/CVE-2019-1197', 'https://github.com/advisories/GHSA-v89p-5hr2-4rh4', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'}
null
{'https://github.com/chakra-core/ChakraCore/commit/bf52b6cfa96d6395046d0aaf87396cd7ca13f6cb', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'}
{'https://github.com/chakra-core/ChakraCore/commit/bf52b6cfa96d6395046d0aaf87396cd7ca13f6cb', 'https://github.com/chakra-core/ChakraCore/commit/6b1250b6ffea7006226dd937e52cf5b353fcfc15'}
GHSA
GHSA-46rx-6jg9-4fh8
Cross-site Scripting in LibreNMS
LibreNMS through 21.10.2 allows XSS via a widget title.
{'CVE-2021-43324'}
2021-11-08T17:59:15Z
2021-11-08T17:59:15Z
MODERATE
6.1
{'CWE-79'}
{'https://github.com/librenms/librenms/commit/99d2462b80435b91a35236639b909eebee432126', 'https://github.com/advisories/GHSA-46rx-6jg9-4fh8', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43324'}
null
{'https://github.com/librenms/librenms/commit/99d2462b80435b91a35236639b909eebee432126'}
{'https://github.com/librenms/librenms/commit/99d2462b80435b91a35236639b909eebee432126'}
GHSA
GHSA-rmj8-8hhh-gv5h
Information Exposure when using Puma with Rails
### Impact Prior to `puma` version `5.6.2`, `puma` may not always call `close` on the response body. Rails, prior to version `7.0.2.2`, depended on the response body being closed in order for its `CurrentAttributes` implementation to work correctly. From Rails: > Under certain circumstances response bodies will not be closed, for example a bug in a webserver[1] or a bug in a Rack middleware. In the event a response is not notified of a close, ActionDispatch::Executor will not know to reset thread local state for the next request. This can lead to data being leaked to subsequent requests, especially when interacting with ActiveSupport::CurrentAttributes. The combination of these two behaviors (Puma not closing the body + Rails' Executor implementation) causes information leakage. ### Patches This problem is fixed in Puma versions 5.6.2 and 4.3.11. This problem is fixed in Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. See: https://github.com/advisories/GHSA-wh98-p28r-vrc9 for details about the rails vulnerability Upgrading to a patched Rails _or_ Puma version fixes the vulnerability. ### Workarounds Upgrade to Rails versions 7.02.2, 6.1.4.6, 6.0.4.6, and 5.2.6.2. The [Rails CVE](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1) includes a middleware that can be used instead. ### References * Rails CVE: [CVE-2022-23633](https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1) ### For more information If you have any questions or comments about this advisory: * Open an issue in [puma](https://github.com/puma/puma) * See our [security policy](https://github.com/puma/puma/security/policy)
{'CVE-2022-23634'}
2022-04-19T19:03:23Z
2022-02-11T21:33:23Z
HIGH
8
{'CWE-200'}
{'https://nvd.nist.gov/vuln/detail/CVE-2022-23634', 'https://github.com/advisories/GHSA-rmj8-8hhh-gv5h', 'https://github.com/puma/puma/security/advisories/GHSA-rmj8-8hhh-gv5h', 'https://github.com/advisories/GHSA-wh98-p28r-vrc9', 'https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb', 'https://groups.google.com/g/ruby-security-ann/c/FkTM-_7zSNA/m/K2RiMJBlBAAJ?utm_medium=email&utm_source=footer&pli=1'}
null
{'https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb'}
{'https://github.com/puma/puma/commit/b70f451fe8abc0cff192c065d549778452e155bb'}
GHSA
GHSA-gh78-48h3-frjq
Improper exception handling in Aedes
An issue was discovered in MoscaJS Aedes 0.42.0 and fixed in 0.42.1. lib/write.js does not properly consider exceptions during the writing of an invalid packet to a stream.
{'CVE-2020-13410'}
2021-05-06T18:10:46Z
2021-05-06T18:10:46Z
HIGH
7.5
{'CWE-755'}
{'https://nvd.nist.gov/vuln/detail/CVE-2020-13410', 'https://github.com/advisories/GHSA-gh78-48h3-frjq', 'https://github.com/moscajs/aedes/pull/493', 'https://payatu.com/advisory/dos-in-aedes-mqtt-broker', 'https://github.com/moscajs/aedes/commit/8d34ee5819cfc983d57e49b45d8c5ef70a76d79b'}
null
{'https://github.com/moscajs/aedes/commit/8d34ee5819cfc983d57e49b45d8c5ef70a76d79b'}
{'https://github.com/moscajs/aedes/commit/8d34ee5819cfc983d57e49b45d8c5ef70a76d79b'}
GHSA
GHSA-36vm-xw34-x4pj
CHECK-fail in `tf.raw_ops.IRFFT`
### Impact An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.IRFFT`: ```python import tensorflow as tf values = [-10.0] * 130 values[0] = -9.999999999999995 inputs = tf.constant(values, shape=[10, 13], dtype=tf.float32) inputs = tf.cast(inputs, dtype=tf.complex64) fft_length = tf.constant([0], shape=[1], dtype=tf.int32) tf.raw_ops.IRFFT(input=inputs, fft_length=fft_length) ``` The above example causes Eigen code to operate on an empty matrix. This triggers on an assertion and causes program termination. ### Patches We have patched the issue in GitHub commit [1c56f53be0b722ca657cbc7df461ed676c8642a2](https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Yakun Zhang and Ying Wang of Baidu X-Team.
{'CVE-2021-29562'}
2021-05-21T14:25:02Z
2021-05-21T14:25:02Z
LOW
2.5
{'CWE-617'}
{'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-36vm-xw34-x4pj', 'https://github.com/advisories/GHSA-36vm-xw34-x4pj', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29562', 'https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2'}
null
{'https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2'}
{'https://github.com/tensorflow/tensorflow/commit/1c56f53be0b722ca657cbc7df461ed676c8642a2'}
GHSA
GHSA-4rmr-c2jx-vx27
Remote code injection in mustache/mustache
In Mustache.php v2.0.0 through v2.14.0, Sections tag can lead to arbitrary php code execution even if strict_callables is true when section value is controllable.
{'CVE-2022-0323'}
2022-01-28T18:22:22Z
2022-01-27T14:51:00Z
HIGH
8.8
{'CWE-1336'}
{'https://nvd.nist.gov/vuln/detail/CVE-2022-0323', 'https://github.com/advisories/GHSA-4rmr-c2jx-vx27', 'https://huntr.dev/bounties/a5f5a988-aa52-4443-839d-299a63f44fb7', 'https://github.com/bobthecow/mustache.php/commit/579ffa5c96e1d292c060b3dd62811ff01ad8c24e'}
null
{'https://github.com/bobthecow/mustache.php/commit/579ffa5c96e1d292c060b3dd62811ff01ad8c24e'}
{'https://github.com/bobthecow/mustache.php/commit/579ffa5c96e1d292c060b3dd62811ff01ad8c24e'}
GHSA
GHSA-f9fq-vjvh-779p
Improper Input Validation in vault-ssh-helper
HashiCorp vault-ssh-helper up to and including version 0.1.6 incorrectly accepted Vault-issued SSH OTPs for the subnet in which a host's network interface was located, rather than the specific IP address assigned to that interface. Fixed in 0.2.0.
{'CVE-2020-24359'}
2022-04-12T22:11:28Z
2022-02-15T01:57:18Z
HIGH
7.5
{'CWE-20'}
{'https://github.com/advisories/GHSA-f9fq-vjvh-779p', 'https://github.com/hashicorp/vault-ssh-helper/blob/master/CHANGELOG.md#020-august-19-2020', 'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f', 'https://nvd.nist.gov/vuln/detail/CVE-2020-24359', 'https://github.com/hashicorp/vault-ssh-helper/releases'}
null
{'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f'}
{'https://github.com/hashicorp/vault-ssh-helper/commit/83effd08cbcbe4b993d776bd9b39465cd9e4603f'}
GHSA
GHSA-h2fg-54x9-5qhq
Nil dereference in NATS JWT, DoS of nats-server
## Problem Description The NATS account system has an Operator trusted by the servers, which signs Accounts, and each Account can then create and sign Users within their account. The Operator should be able to safely issue Accounts to other entities which it does not fully trust. A malicious Account could create and sign a User JWT with a state not created by the normal tooling, such that decoding by the NATS JWT library (written in Go) would attempt a nil dereference, aborting execution. The NATS Server is known to be impacted by this. ## Affected versions #### JWT library * all versions prior to 1.1.0 #### NATS Server * Version 2 prior to 2.1.9 ## Impact #### JWT library * Programs would nil dereference and panic, aborting execution by default. #### NATS server * Denial of Service caused by process termination ## Workaround If your NATS servers do not trust any accounts which are managed by untrusted entities, then malformed User credentials are unlikely to be encountered. ## Solution Upgrade the JWT dependency in any application using it. Upgrade the NATS server if using NATS Accounts.
{'CVE-2020-26521'}
2022-02-11T23:43:22Z
2022-02-11T23:43:13Z
LOW
7.5
{'CWE-476'}
{'https://github.com/nats-io/jwt/security/advisories/GHSA-h2fg-54x9-5qhq', 'http://www.openwall.com/lists/oss-security/2020/11/02/2', 'https://github.com/advisories/GHSA-h2fg-54x9-5qhq', 'https://github.com/nats-io/nats-server/commits/master', 'https://nvd.nist.gov/vuln/detail/CVE-2020-26521', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VT67XCLIIBYRT762SVFBYFFTQFVSM3SI/', 'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168', 'https://advisories.nats.io/CVE/CVE-2020-26521.txt'}
null
{'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168'}
{'https://github.com/nats-io/nats-server/commit/9ff8bcde2e46009e98bd9e88f598af355f62c168'}
GHSA
GHSA-7r87-cj48-wj45
Potential Captcha Validate Bypass in flask-session-captcha
### Impact flask-session-captcha is a package which allows users to extend Flask by adding an image based captcha stored in a server side session. The `captcha.validate()` function would return `None` if passed no value (e.g. by submitting a request with an empty form). If implementing users were checking the return value to be **False**, the captcha verification check could be bypassed. Sample vulnerable code: ```python if captcha.validate() == False: ... # abort else: ... # do stuff ``` ### Patches A new version (1.2.1) is available that fixes the issue. ### Workarounds Users can workaround the issue by not explicitly checking that the value is False. Checking the return value less explicitly should still work. ```python if not captcha.validate(): ... # abort else: ... # do stuff ``` ```python if captcha.validate(): ... # do stuff else: ... # abort ``` ### References https://github.com/Tethik/flask-session-captcha/pull/27 ### For more information If you have any questions or comments about this advisory: * Open an issue in [the github repo](https://github.com/Tethik/flask-session-captcha)
{'CVE-2022-24880'}
2022-04-27T18:18:03Z
2022-04-26T21:19:52Z
MODERATE
5.3
{'CWE-754', 'CWE-394', 'CWE-253'}
{'https://github.com/advisories/GHSA-7r87-cj48-wj45', 'https://nvd.nist.gov/vuln/detail/CVE-2022-24880', 'https://github.com/Tethik/flask-session-captcha/commit/2811ae23a38d33b620fb7a07de8837c6d65c13e4', 'https://github.com/Tethik/flask-session-captcha/security/advisories/GHSA-7r87-cj48-wj45', 'https://github.com/Tethik/flask-session-captcha/releases/tag/v1.2.1', 'https://github.com/Tethik/flask-session-captcha/pull/27'}
null
{'https://github.com/Tethik/flask-session-captcha/commit/2811ae23a38d33b620fb7a07de8837c6d65c13e4'}
{'https://github.com/Tethik/flask-session-captcha/commit/2811ae23a38d33b620fb7a07de8837c6d65c13e4'}
GHSA
GHSA-3xv8-3j54-hgrp
Out-of-bounds read in Pillow
In libImaging/PcxDecode.c in Pillow before 6.2.3 and 7.x before 7.0.1, an out-of-bounds read can occur when reading PCX files where state->shuffle is instructed to read beyond state->buffer.
{'CVE-2020-10378'}
2021-11-03T18:04:53Z
2021-11-03T18:04:53Z
MODERATE
5.5
{'CWE-125'}
{'https://github.com/python-pillow/Pillow/commits/master/src/libImaging', 'https://github.com/pypa/advisory-db/blob/7872b0a91b4d980f749e6d75a81f8cc1af32829f/vulns/pillow/PYSEC-2020-77.yaml', 'https://nvd.nist.gov/vuln/detail/CVE-2020-10378', 'https://pillow.readthedocs.io/en/stable/releasenotes/6.2.3.html', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HOKHNWV2VS5GESY7IBD237E7C6T3I427/', 'https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BEBCPE4F2VHTIT6EZA2YZQZLPVDEBJGD/', 'https://github.com/advisories/GHSA-3xv8-3j54-hgrp', 'https://github.com/python-pillow/Pillow/commit/6a83e4324738bb0452fbe8074a995b1c73f08de7#diff-9478f2787e3ae9668a15123b165c23ac', 'https://usn.ubuntu.com/4430-2/', 'https://pillow.readthedocs.io/en/stable/releasenotes/7.1.0.html', 'https://usn.ubuntu.com/4430-1/', 'https://github.com/python-pillow/Pillow/pull/4538'}
null
{'https://github.com/python-pillow/Pillow/commit/6a83e4324738bb0452fbe8074a995b1c73f08de7#diff-9478f2787e3ae9668a15123b165c23ac'}
{'https://github.com/python-pillow/Pillow/commit/6a83e4324738bb0452fbe8074a995b1c73f08de7#diff-9478f2787e3ae9668a15123b165c23ac'}
GHSA
GHSA-5q7q-qqw2-hjq7
Cross-Site Scripting in AjaxNetProfessional
### Overview Affected versions of this package are vulnerable to Deserialization of Untrusted Data due to the possibility of deserialization of arbitrary JavaScript objects. ### Description Cross-Site Scripting (XSS) attacks are a type of injection, in which malicious scripts are injected into otherwise benign and trusted websites. XSS attacks occur when an attacker uses a web application to send malicious code, generally in the form of a browser side script, to a different end user. Flaws that allow these attacks to succeed are quite widespread and occur anywhere a web application uses input from a user within the output it generates without validating or encoding it. XSS effects vary in range from petty nuisance to significant security risk, depending on the sensitivity of the data handled by the vulnerable site and the nature of any security mitigation implemented by the site's owner network. ### Releases Releases before version 21.12.22.1 are affected. Please be careful to download any binary DLL from other web sites, especially we found NuGet packages not owned by us that contain vulnerable versions. ### Workarounds A workaround exists that replaces one of the core JavaScript files embedded in the library. Using a XML configuration allows to replace the default JavaScript code to be replaced with the version on GitHub. ```xml <configuration> <configSections> <sectionGroup name="ajaxNet"> <section name="ajaxSettings" type="AjaxPro.AjaxSettingsSectionHandler,AjaxPro.2" requirePermission="false" restartOnExternalChanges="true"/> </sectionGroup> </configSections> <ajaxNet> <ajaxSettings> <coreScript>~/ajaxpro-core-fixed.js</coreScript> </ajaxSettings> </ajaxNet> </configuration> ``` Copy the file core.js from the main project folder to your web server root folder and rename that ajaxpro-core-fixed.js. Clients need to refresh the web page to download the changed JavaScript code. ### References Commit fixing the issue: c89e39b9679fcb8ab6644fe21cc7e652cb615e2b Note: the official Ajax.NET Professional (AjaxPro) NuGet package is available here: https://www.nuget.org/packages/AjaxNetProfessional/ ### For more information If you have any questions or comments about this advisory: * Open an issue on this GitHub repository
{'CVE-2021-43853'}
2022-04-19T19:03:18Z
2022-01-06T18:32:24Z
HIGH
8.7
{'CWE-79'}
{'https://github.com/michaelschwarz/Ajax.NET-Professional/commit/c89e39b9679fcb8ab6644fe21cc7e652cb615e2b', 'https://nvd.nist.gov/vuln/detail/CVE-2021-43853', 'https://github.com/michaelschwarz/Ajax.NET-Professional/security/advisories/GHSA-5q7q-qqw2-hjq7', 'https://github.com/michaelschwarz/Ajax.NET-Professional/releases/tag/v21.12.22.1', 'https://github.com/advisories/GHSA-5q7q-qqw2-hjq7'}
null
{'https://github.com/michaelschwarz/Ajax.NET-Professional/commit/c89e39b9679fcb8ab6644fe21cc7e652cb615e2b'}
{'https://github.com/michaelschwarz/Ajax.NET-Professional/commit/c89e39b9679fcb8ab6644fe21cc7e652cb615e2b'}
GHSA
GHSA-pmpr-55fj-r229
Division by zero in TFLite's implementation of `SVDF`
### Impact The implementation of the `SVDF` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/7f283ff806b2031f407db64c4d3edcda8fb9f9f5/tensorflow/lite/kernels/svdf.cc#L99-L102): ```cc const int rank = params->rank; ... TF_LITE_ENSURE_EQ(context, num_filters % rank, 0); ``` An attacker can craft a model such that `params->rank` would be 0. ### Patches We have patched the issue in GitHub commit [6841e522a3e7d48706a02e8819836e809f738682](https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
{'CVE-2021-29598'}
2021-05-21T14:27:58Z
2021-05-21T14:27:58Z
LOW
2.5
{'CWE-369'}
{'https://github.com/advisories/GHSA-pmpr-55fj-r229', 'https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pmpr-55fj-r229', 'https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682', 'https://nvd.nist.gov/vuln/detail/CVE-2021-29598'}
null
{'https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682'}
{'https://github.com/tensorflow/tensorflow/commit/6841e522a3e7d48706a02e8819836e809f738682'}
GHSA
GHSA-c9c5-9fpr-m882
Moderate severity vulnerability that affects sentry-raven
The numtok function in lib/raven/okjson.rb in the raven-ruby gem before 0.12.2 for Ruby allows remote attackers to cause a denial of service via a large exponent value in a scientific number.
{'CVE-2014-9490'}
2021-09-08T21:58:29Z
2017-10-24T18:33:36Z
MODERATE
0
null
{'https://groups.google.com/forum/#!topic/getsentry/Cz5bih0ZY1U', 'http://seclists.org/oss-sec/2015/q1/26', 'https://exchange.xforce.ibmcloud.com/vulnerabilities/99687', 'https://github.com/getsentry/raven-ruby/commit/477ee93a3f735be33bc1e726820654cdf6e22d8f', 'https://github.com/advisories/GHSA-c9c5-9fpr-m882', 'https://nvd.nist.gov/vuln/detail/CVE-2014-9490'}
null
{'https://github.com/getsentry/raven-ruby/commit/477ee93a3f735be33bc1e726820654cdf6e22d8f'}
{'https://github.com/getsentry/raven-ruby/commit/477ee93a3f735be33bc1e726820654cdf6e22d8f'}
GHSA
GHSA-m7rg-8wvq-846v
Prototype pollution
Prototype pollution vulnerability in 'nestie' versions 0.0.0 through 1.0.0 allows an attacker to cause a denial of service and may lead to remote code execution.
{'CVE-2021-25947'}
2021-06-14T21:47:45Z
2021-06-07T21:49:14Z
CRITICAL
9.8
{'CWE-1321'}
{'https://github.com/lukeed/nestie/commit/bc80d5898d1e5e8a3d325d355eda0c325c8dcfc2', 'https://github.com/advisories/GHSA-m7rg-8wvq-846v', 'https://nvd.nist.gov/vuln/detail/CVE-2021-25947', 'https://www.whitesourcesoftware.com/vulnerability-database/CVE-2021-25947'}
null
{'https://github.com/lukeed/nestie/commit/bc80d5898d1e5e8a3d325d355eda0c325c8dcfc2'}
{'https://github.com/lukeed/nestie/commit/bc80d5898d1e5e8a3d325d355eda0c325c8dcfc2'}
GHSA
GHSA-657m-v5vm-f6rw
Cross-Site-Request-Forgery in Backend
> ### Meta > * CVSS: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C` (8.2) ### Problem It has been discovered that the new TYPO3 v11 feature that allows users to create and share [deep links in the backend user interface](https://typo3.org/article/typo3-version-112-escape-the-orbit#c12178) is vulnerable to cross-site-request-forgery. The impact is the same as described in [TYPO3-CORE-SA-2020-006 (CVE-2020-11069)](https://typo3.org/security/advisory/typo3-core-sa-2020-006). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system. To successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time. The following [Same-Site cookie settings](https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.7.x/Feature-90351-ConfigureTYPO3-shippedCookiesWithSameSiteFlag.html) in _$GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite]_ are required for an attack to be successful: * _SameSite=_***strict***: malicious evil.**example.org** invoking TYPO3 application at good.**example.org** * _SameSite=_***lax*** or ***none***: malicious **evil.com** invoking TYPO3 application at **example.org** ### Solution Update your instance to TYPO3 version 11.5.0 which addresses the problem described. ### Credits Thanks to Richie Lee who reported this issue and to TYPO3 core & security team members Benni Mack and Oliver Hader who fixed the issue. ### References * [TYPO3-CORE-SA-2021-014](https://typo3.org/security/advisory/typo3-core-sa-2021-014) * [CVE-2020-11069](https://nvd.nist.gov/vuln/detail/CVE-2020-11069) reintroduced in TYPO3 v11.2.0
{'CVE-2021-41113'}
2022-04-19T19:03:11Z
2021-10-05T20:23:47Z
MODERATE
8.8
{'CWE-352', 'CWE-309'}
{'https://typo3.org/security/advisory/typo3-core-sa-2020-006', 'https://nvd.nist.gov/vuln/detail/CVE-2020-11069', 'https://github.com/TYPO3/typo3/commit/fa51999203c5e5d913ecae5ea843ccb2b95fa33f', 'https://github.com/TYPO3/typo3/security/advisories/GHSA-657m-v5vm-f6rw', 'https://github.com/advisories/GHSA-657m-v5vm-f6rw', 'https://nvd.nist.gov/vuln/detail/CVE-2021-41113'}
null
{'https://github.com/TYPO3/typo3/commit/fa51999203c5e5d913ecae5ea843ccb2b95fa33f'}
{'https://github.com/TYPO3/typo3/commit/fa51999203c5e5d913ecae5ea843ccb2b95fa33f'}
GHSA
GHSA-6jqj-f58p-mrw3
Denial of Service in TenderMint
### Description **Denial of Service** Tendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network. Tendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit. **False Witness** Tendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **. _** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._ This can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this. Tendermint 0.33.6 verifies all the signatures during block execution ***. _*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._ ### Impact - All nodes - The network stops due to having a commit with a wrong signature. ### Patches - v0.33.6 ### Workarounds No workarounds. ### References - https://github.com/tendermint/tendermint/issues/4926 ### For more information If you have any questions or comments about this advisory: * Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint) * Email us at [security@tendermint.com](mailto:security@tendermint.com) More information can be found [here](https://tendermint.com/security/).
{'CVE-2020-15091'}
2022-04-19T19:02:29Z
2021-12-20T18:17:33Z
MODERATE
6.5
{'CWE-347'}
{'https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3', 'https://github.com/advisories/GHSA-6jqj-f58p-mrw3', 'https://nvd.nist.gov/vuln/detail/CVE-2020-15091', 'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340', 'https://github.com/tendermint/tendermint/issues/4926'}
null
{'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340'}
{'https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340'}
GHSA
GHSA-4p3x-8qw9-24w9
Authenticated Stored XSS in shopware/shopware
### Impact Authenticated Stored XSS in Administration ### Patches Use the Security Plugin: https://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html ### Workarounds If you cannot use the security plugin, add the following config to your `.htaccess` file ``` <IfModule mod_headers.c> <FilesMatch "\.(?i:svg)$"> Header set Content-Security-Policy "script-src 'none'" </FilesMatch> </IfModule> ``` If you are using nginx as server config, you can add the following to your configuration: ``` server { # ... location ~* ^.+\.svg$ { add_header Content-Security-Policy "script-src 'none'"; } } ``` ### References https://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021
{'CVE-2021-41188'}
2021-10-29T13:49:23Z
2021-10-27T18:53:18Z
MODERATE
5.7
{'CWE-79'}
{'https://nvd.nist.gov/vuln/detail/CVE-2021-41188', 'https://store.shopware.com/en/swag575294366635f/shopware-security-plugin.html', 'https://github.com/shopware/shopware/commit/37213e91d525c95df262712cba80d1497e395a58', 'https://docs.shopware.com/en/shopware-5-en/sicherheitsupdates/security-update-10-2021', 'https://github.com/shopware/shopware/releases/tag/v5.7.6', 'https://github.com/advisories/GHSA-4p3x-8qw9-24w9', 'https://github.com/shopware/shopware/security/advisories/GHSA-4p3x-8qw9-24w9'}
null
{'https://github.com/shopware/shopware/commit/37213e91d525c95df262712cba80d1497e395a58'}
{'https://github.com/shopware/shopware/commit/37213e91d525c95df262712cba80d1497e395a58'}