🚨 [security] [backend] Update axios 0.22.0 → 1.7.5 (major)

[depfu]

---

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

---

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ axios (0.22.0 → 1.7.5) · Repo · Changelog

Security Advisories 🚨

🚨 Server-Side Request Forgery in axios

axios 1.7.2 allows SSRF via unexpected behavior where requests for path relative URLs get processed as protocol relative URLs.

🚨 Axios Cross-Site Request Forgery Vulnerability

An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.

🚨 Axios Cross-Site Request Forgery Vulnerability

An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ follow-redirects (indirect, 1.14.4 → 1.15.6) · Repo

Security Advisories 🚨

🚨 follow-redirects' Proxy-Authorization header kept across hosts

When using axios, its dependency follow-redirects only clears authorization header during cross-domain redirect, but allows the proxy-authentication header which contains credentials too.

Steps To Reproduce & PoC

Test code:

const axios = require('axios');
axios.get('http://127.0.0.1:10081/', {

headers: {

'AuThorization': 'Rear Test',

'ProXy-AuthoriZation': 'Rear Test',

'coOkie': 't=1'

}

})

.then((response) => {

console.log(response);

})

When I meet the cross-domain redirect, the sensitive headers like authorization and cookie are cleared, but proxy-authentication header is kept.

Impact

This vulnerability may lead to credentials leak.

Recommendations

Remove proxy-authentication header during cross-domain redirect

Recommended Patch

follow-redirects/index.js:464

- removeMatchingHeaders(/^(?:authorization|cookie)$/i, this._options.headers);
+ removeMatchingHeaders(/^(?:authorization|proxy-authorization|cookie)$/i, this._options.headers);

🚨 Follow Redirects improperly handles URLs in the url.parse() function

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.

🚨 Exposure of Sensitive Information to an Unauthorized Actor in follow-redirects

Exposure of Sensitive Information to an Unauthorized Actor in NPM follow-redirects prior to 1.14.8.

🚨 Exposure of sensitive information in follow-redirects

follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor

Commits

See the full diff on Github. The new version differs by 45 commits:

• Release version 1.15.6 of the npm package.
• Drop Proxy-Authorization across hosts.
• Use GitHub for disclosure.
• Release version 1.15.5 of the npm package.
• Preserve fragment in responseUrl.
• Release version 1.15.4 of the npm package.
• Disallow bracketed hostnames.
• Prefer native URL instead of deprecated url.parse.
• Prefer native URL instead of legacy url.resolve.
• Simplify _processResponse error handling.
• Add bracket tests.
• Do not directly set Error properties.
• Release version 1.15.3 of the npm package.
• Fix resource leak on destroy.
• Split linting and testing.
• build: harden ci.yml permissions
• Release version 1.15.2 of the npm package.
• Default to localhost if no host given.
• Throw invalid URL error on relative URLs.
• Use type functions.
• ternary operator syntax fix
• HTTP header lines are separated by CRLF.
• Create SECURITY.md (#202)
• Release version 1.15.1 of the npm package.
• Use for ... of.
• Fix redirecting to relative URL when using proxy
• Release version 1.15.0 of the npm package.
• Add headers to request details
• Pass status & request details to beforeRedirect (#198)
• Test on Node 18.
• refactor: replace deprecated String.prototype.substr() (#196)
• Release version 1.14.9 of the npm package.
• Keep headers when upgrading from HTTP to HTTPS.
• Reduce nesting.
• Release version 1.14.8 of the npm package.
• Drop confidential headers across schemes.
• Release version 1.14.7 of the npm package.
• Drop Cookie header across domains.
• Release version 1.14.6 of the npm package.
• Ignore null headers.
• Release version 1.14.5 of the npm package.
• Make compatible with Node 17.
• Fix: clear internal timer on request abort to avoid leakage
• Keep Authorization header on subdomain redirects.
• Carry over Host header on relative redirects (#172)

🆕 asynckit (added, 0.4.0)

🆕 combined-stream (added, 1.0.8)

🆕 delayed-stream (added, 1.0.0)

🆕 form-data (added, 4.0.0)

🆕 proxy-from-env (added, 1.1.0)

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)