Fix 7 vulnerable dependencies identified by Prisma Cloud #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![prisma-cloud-devsecops[bot]](https://avatars.githubusercontent.com/in/135857?s=60&v=4){kind=small}
packages/requirements.txt
Outdated
| @@ -1,2 +1,2 @@ | |||
| django==1.2 | |||
| django == 3.2.4 | |||
There was a problem hiding this comment.
django 3.2.4 / requirements.txt
Total vulnerabilities: 19
| Critical: 5 | High: 12 | Medium: 2 | Low: 0 |
|---|
| Vulnerability ID | Severity | CVSS | Fixed in | Status |
|---|---|---|---|---|
| CVE-2021-35042 |  CRITICAL |
9.8 | 3.2.5 |
Open |
| CVE-2022-28346 | CRITICAL |
9.8 | 3.2.13 |
Open |
| CVE-2022-28347 | CRITICAL |
9.8 | 3.2.13 |
Open |
| CVE-2022-34265 | CRITICAL |
9.8 | 3.2.14 |
Open |
| CVE-2023-31047 | CRITICAL |
9.8 | 3.2.19 |
Open |
| CVE-2023-41164 |  HIGH |
7.5 | 3.2.21 |
Open |
| CVE-2023-43665 | HIGH |
7.5 | 3.2.22 |
Open |
| CVE-2023-46695 | HIGH |
7.5 | 3.2.23 |
Open |
| CVE-2021-45116 | HIGH |
7.5 | 3.2.11 |
Open |
| CVE-2021-45115 | HIGH |
7.5 | 3.2.11 |
Open |
| CVE-2021-44420 | HIGH |
7.3 | 3.2.10 |
Open |
| CVE-2022-23833 | HIGH |
7.5 | 3.2.12 |
Open |
| CVE-2022-36359 | HIGH |
8.8 | 3.2.15 |
Open |
| CVE-2022-41323 | HIGH |
7.5 | 3.2.16 |
Open |
| CVE-2023-23969 | HIGH |
7.5 | 3.2.17 |
Open |
| CVE-2023-24580 | HIGH |
7.5 | 3.2.18 |
Open |
| CVE-2023-36053 | HIGH |
7.5 | 3.2.20 |
Open |
| CVE-2021-45452 |  MEDIUM |
5.3 | 3.2.11 |
Open |
| CVE-2022-22818 | MEDIUM |
6.1 | 3.2.12 |
Open |
| @@ -1,2 +1,2 @@ | |||
| django==1.2 | |||
| django == 3.2.4 | |||
There was a problem hiding this comment.
django 3.2.4 / requirements.txt
Total vulnerabilities: 19
| Critical: 5 | High: 12 | Medium: 2 | Low: 0 |
|---|
| Vulnerability ID | Severity | CVSS | Fixed in | Status |
|---|---|---|---|---|
| CVE-2021-35042 | CRITICAL |
9.8 | 3.2.5 |
Open |
| CVE-2022-28346 | CRITICAL |
9.8 | 3.2.13 |
Open |
| CVE-2022-28347 | CRITICAL |
9.8 | 3.2.13 |
Open |
| CVE-2022-34265 | CRITICAL |
9.8 | 3.2.14 |
Open |
| CVE-2023-31047 | CRITICAL |
9.8 | 3.2.19 |
Open |
| CVE-2023-41164 | HIGH |
7.5 | 3.2.21 |
Open |
| CVE-2023-43665 | HIGH |
7.5 | 3.2.22 |
Open |
| CVE-2023-46695 | HIGH |
7.5 | 3.2.23 |
Open |
| CVE-2021-45116 | HIGH |
7.5 | 3.2.11 |
Open |
| CVE-2021-45115 | HIGH |
7.5 | 3.2.11 |
Open |
| CVE-2021-44420 | HIGH |
7.3 | 3.2.10 |
Open |
| CVE-2022-23833 | HIGH |
7.5 | 3.2.12 |
Open |
| CVE-2022-36359 | HIGH |
8.8 | 3.2.15 |
Open |
| CVE-2022-41323 | HIGH |
7.5 | 3.2.16 |
Open |
| CVE-2023-23969 | HIGH |
7.5 | 3.2.17 |
Open |
| CVE-2023-24580 | HIGH |
7.5 | 3.2.18 |
Open |
| CVE-2023-36053 | HIGH |
7.5 | 3.2.20 |
Open |
| CVE-2021-45452 | MEDIUM |
5.3 | 3.2.11 |
Open |
| CVE-2022-22818 | MEDIUM |
6.1 | 3.2.12 |
Open |
packages/sub/pom.xml
Outdated
| @@ -40,12 +40,12 @@ | |||
| <dependency> | |||
| <groupId>org.apache.commons</groupId> | |||
| <artifactId>commons-compress</artifactId> | |||
| <version>1.20</version> | |||
| <version>1.21</version> | |||
| </dependency> | |||
| <dependency> | |||
There was a problem hiding this comment.
org.springframework:spring-core 6.0.8 / pom.xml
Total vulnerabilities: 2
| Critical: 1 | High: 1 | Medium: 0 | Low: 0 |
|---|
| Vulnerability ID | Severity | CVSS | Fixed in | Status |
|---|---|---|---|---|
| CVE-2023-44794 | CRITICAL |
9.8 | - |
Open |
| CVE-2023-34053 | HIGH |
7.5 | 6.0.14 |
Open |
bridgeit-devops-bot
force-pushed
the
pcc-vulnerability-fixes
branch
from
90d6e9a
to
75554fa
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prisma Cloud has detected new vulnerabilities or dependencies in the scan performed on Thu, 04 Jan 2024 07:09:22 UTC
This PR includes the fixes for the vulnerabilities discovered below:
DOMParserandXMLSerializermodule. xmldom parses XML that is not well-formed because it contains multiple top level elements, and adds all root nodes to thechildNodescollection of theDocument, without reporting any error or throwing. This breaks the assumption that there is only a single root node in the tree, which led to issuance of CVE-2022-39299 as it is a potential issue for dependents. Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag latest) or @xmldom/xmldom@>=0.9.0-beta.4 (dist-tag next). As a workaround, please one of the following approaches depending on your use case: instead of searching for elements in the whole DOM, only search in thedocumentElementor reject a document with a document that has more then 1childNode.@babel/traverseprior to versions 7.23.2 and 8.0.0-alpha.4 and all versions ofbabel-traverse, using Babel to compile code that was specifically crafted by an attacker can lead to arbitrary code execution during compilation, when using plugins that rely on thepath.evaluate()orpath.evaluateTruthy()internal Babel methods. Known affected plugins are@babel/plugin-transform-runtime;@babel/preset-envwhen using itsuseBuiltInsoption; and any "polyfill provider" plugin that depends on@babel/helper-define-polyfill-provider, such asbabel-plugin-polyfill-corejs3,babel-plugin-polyfill-corejs2,babel-plugin-polyfill-es-shims,babel-plugin-polyfill-regenerator. No other plugins under the@babel/namespace are impacted, but third-party plugins might be. Users that only compile trusted code are not impacted. The vulnerability has been fixed in@babel/traverse@7.23.2and@babel/traverse@8.0.0-alpha.4. Those who cannot upgrade@babel/traverseand are using one of the affected packages mentioned above should upgrade them to their latest version to avoid triggering the vulnerable code path in affected@babel/traverseversions:@babel/plugin-transform-runtimev7.23.2,@babel/preset-envv7.23.2,@babel/helper-define-polyfill-providerv0.4.3,babel-plugin-polyfill-corejs2v0.4.6, `babel-plugin-polyfill-cDOMParserandXMLSerializermodule. xmldom parses XML that is not well-formed because it contains multiple top level elements, and adds all root nodes to thechildNodescollection of theDocument, without reporting any error or throwing. This breaks the assumption that there is only a single root node in the tree, which led to issuance of CVE-2022-39299 as it is a potential issue for dependents. Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag latest) or @xmldom/xmldom@>=0.9.0-beta.4 (dist-tag next). As a workaround, please one of the following approaches depending on your use case: instead of searching for elements in the whole DOM, only search in thedocumentElementor reject a document with a document that has more then 1childNode.Proxy. As a result a threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version3.9.18ofvm2. Users are advised to upgrade. There are no known workarounds for this vulnerability.handleException()and leak unsanitized host exceptions which can be used to escape the sandbox and run arbitrary code in host context. A threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version3.9.16ofvm2.Error.prepareStackTracein case of unhandled async errors. A threat actor could bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.15 of vm2. There are no known workarounds.DOMParserandXMLSerializermodule. xmldom parses XML that is not well-formed because it contains multiple top level elements, and adds all root nodes to thechildNodescollection of theDocument, without reporting any error or throwing. This breaks the assumption that there is only a single root node in the tree, which led to issuance of CVE-2022-39299 as it is a potential issue for dependents. Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag latest) or @xmldom/xmldom@>=0.9.0-beta.4 (dist-tag next). As a workaround, please one of the following approaches depending on your use case: instead of searching for elements in the whole DOM, only search in thedocumentElementor reject a document with a document that has more then 1childNode.parsemethod of the JSON5 library before and including versions 1.0.1 and 2.2.1 does not restrict parsing of keys named__proto__, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned byJSON5.parseand not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned fromJSON5.parse. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution.JSON5.parseshould restrict parsing of__proto__keys when parsing JSON strings to objects. As a point of reference, theJSON.parsemethod included in JavaScript ignores__proto__keys. Simply changingJSON5.parsetoJSON.parsein the examples above mitigates this vulnerability. This vulnerability is patched in json5 verinline.reflinkSearchmay cause catastrophic backtracking against some strings and lead to a denial of service (DoS). Anyone who runs untrusted markdown through a vulnerable version of marked and does not use a worker with a time limit may be affected. This issue is patched in version 4.0.10. As a workaround, avoid running untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.block.defmay cause catastrophic backtracking against some strings and lead to a regular expression denial of service (ReDoS). Anyone who runs untrusted markdown through a vulnerable version of marked and does not use a worker with a time limit may be affected. This issue is patched in version 4.0.10. As a workaround, avoid running untrusted markdown through marked or run marked on a worker thread and set a reasonable time limit to prevent draining resources.node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding aDigestInfoASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used. The issue has been addressed innode-forgeversion 1.3.0. There are currently no known workarounds.node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed innode-forgeversion 1.3.0. There are currently no known workarounds.engine.iopackage starting from version4.0.0, including those who uses depending packages likesocket.io. Versions prior to4.0.0are not impacted. A fix has been released for each major branch, namely4.1.2for the4.x.xbranch,5.2.1for the5.x.xbranch, and6.1.1for the6.x.xbranch. There is no known workaround except upgrading to a safe version.shell.exec()may be visible to other users on the same system. You may be affected if you executeshell.exec()in multi-user Mac, Linux, or WSL environments, or if you executeshell.exec()as the root user. Other shelljs functions (including the asynchronous version ofshell.exec()) are not impacted. ### Patches Patched in shelljs 0.8.5 ### Workarounds Recommended action is to upgrade to 0.8.5. ### References https://huntr.dev/bounties/50996581-c08e-4eed-a90e-c0bac082679c/ ### For more information If you have any questions or comments about this advisory: * Ask at shelljs/shelljs#1058 * Open an issue at https://github.com/shelljs/shelljs/issues/newnode-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not properly checkDigestInfofor a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest. The issue has been addressed innode-forgeversion 1.3.0. There are currently no known workarounds.socket.ioparent package. Older versions are not impacted. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of theengine.iopackage, including those who use depending packages likesocket.io. This issue was fixed in version 6.4.2 of Engine.IO. There is no known workaround except upgrading to a safe version.core.exportVariablefunction uses a well known delimiter that attackers can use to break out of that specific variable and assign values to other arbitrary variables. Workflows that write untrusted values to theGITHUB_ENVfile may cause the path or other environment variables to be modified without the intention of the workflow or action author. Users should upgrade to@actions/core v1.9.1. If you are unable to upgrade the@actions/corepackage, you can modify your action to ensure that any user input does not contain the delimiter_GitHubActionsFileCommandDelimeter_before callingcore.exportVariable.inspectmethod and edit options forconsole.log. As a result a threat actor can edit options for theconsole.logcommand. This vulnerability was patched in the release of version3.9.18ofvm2. Users are advised to upgrade. Users unable to upgrade may make theinspectmethod readonly withvm.readonly(inspect)after creating a vm.forge.util.parseUrlAPI would not properly parse certain inputs resulting in a parsed data structure that could lead to undesired behavior. ### Patchesforge.util.parseUrland other very old related URL APIs were removed in 1.0.0 in favor of letting applications use the more modern WHATWG URL Standard API. ### Workarounds Ensure code does not directly or indirectly callforge.util.parseUrlwith untrusted input. ### References - https://www.huntr.dev/bounties/41852c50-3c6d-4703-8c55-4db27164a4ae/ ### For more information If you have any questions or comments about this advisory: * Open an issue in forge * Email us at support@digitalbazaar.comforge.debugAPI had a potential prototype pollution issue if called with untrusted input. The API was only used for internal debug purposes in a safe way and never documented or advertised. It is suspected that uses of this API, if any exist, would likely not have used untrusted inputs in a vulnerable way. ### Patches Theforge.debugAPI and related functions were removed in 1.0.0. ### Workarounds Don't use theforge.debugAPI directly or indirectly with untrusted input. ### References - https://www.huntr.dev/bounties/1-npm-node-forge/ ### For more information If you have any questions or comments about this advisory: * Open an issue in forge. * Email us at support@digitalbazaar.com.