-
Notifications
You must be signed in to change notification settings - Fork 0
Update devsecops-mvp.yml #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
subhashbohra
wants to merge
1
commit into
main
Choose a base branch
from
subhashbohra-patch-8
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or 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
🛡️ AI DevSecOps Scan Summary✅ Dependency scan completed. 📊 Vulnerability Report🔍 Dependency Vulnerability Report%0A%0A| axios | CVE-2021-3749 | HIGH | nodejs-axios: Regular expression denial of service in trim function | Fixed: 0.21.2 |%0A| axios | CVE-2025-27152 | HIGH | axios: Possible SSRF and Credential Leakage via Absolute URL in axios Requests | Fixed: 1.8.2, 0.30.0 |%0A| axios | CVE-2025-58754 | HIGH | axios: Axios DoS via lack of data size check | Fixed: 1.12.0 |%0A| axios | CVE-2020-28168 | MEDIUM | nodejs-axios: allows an attacker to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address | Fixed: 0.21.1 |%0A| axios | CVE-2023-45857 | MEDIUM | axios: exposure of confidential data stored in cookies | Fixed: 1.6.0, 0.28.0 |%0A| body-parser | CVE-2024-45590 | HIGH | body-parser: Denial of Service Vulnerability in body-parser | Fixed: 1.20.3 |%0A| cookie | CVE-2024-47764 | LOW | cookie: cookie accepts cookie name, path, and domain with out of bounds characters | Fixed: 0.7.0 |%0A| crypto-js | CVE-2023-46233 | CRITICAL | crypto-js: PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard | Fixed: 4.2.0 |%0A| crypto-js | CVE-2020-36732 | MEDIUM | crypto-js uses insecure random numbers | Fixed: 3.2.1 |%0A| express | CVE-2024-29041 | MEDIUM | express: cause malformed URLs to be evaluated | Fixed: 4.19.2, 5.0.0-beta.3 |%0A| express | CVE-2024-43796 | LOW | express: Improper Input Handling in Express Redirects | Fixed: 4.20.0, 5.0.0 |%0A| follow-redirects | CVE-2022-0155 | HIGH | follow-redirects: Exposure of Private Personal Information to an Unauthorized Actor | Fixed: 1.14.7 |%0A| follow-redirects | CVE-2022-0536 | MEDIUM | follow-redirects: Exposure of Sensitive Information via Authorization Header leak | Fixed: 1.14.8 |%0A| follow-redirects | CVE-2023-26159 | MEDIUM | follow-redirects: Improper Input Validation due to the improper handling of URLs by the url.parse() | Fixed: 1.15.4 |%0A| follow-redirects | CVE-2024-28849 | MEDIUM | follow-redirects: Possible credential leak | Fixed: 1.15.6 |%0A| form-data | CVE-2025-7783 | CRITICAL | form-data: Unsafe random function in form-data | Fixed: 2.5.4, 3.0.4, 4.0.4 |%0A| jsonwebtoken | CVE-2022-23539 | HIGH | jsonwebtoken: Unrestricted key type could lead to legacy keys usagen | Fixed: 9.0.0 |%0A| jsonwebtoken | CVE-2022-23540 | MEDIUM | jsonwebtoken: Insecure default algorithm in jwt.verify() could lead to signature validation bypass | Fixed: 9.0.0 |%0A| jsonwebtoken | CVE-2022-23541 | MEDIUM | jsonwebtoken: Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC | Fixed: 9.0.0 |%0A| lodash | CVE-2021-23337 | HIGH | nodejs-lodash: command injection via template | Fixed: 4.17.21 |%0A| lodash | CVE-2020-28500 | MEDIUM | nodejs-lodash: ReDoS via the toNumber, trim and trimEnd functions | Fixed: 4.17.21 |%0A| multer | CVE-2025-47935 | HIGH | Multer vulnerable to Denial of Service via memory leaks from unclosed streams | Fixed: 2.0.0 |%0A| path-to-regexp | CVE-2024-45296 | HIGH | path-to-regexp: Backtracking regular expressions cause ReDoS | Fixed: 1.9.0, 0.1.10, 8.0.0, 3.3.0, 6.3.0 |%0A| path-to-regexp | CVE-2024-52798 | HIGH | path-to-regexp: path-to-regexp Unpatched
|
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.
No description provided.