CVE-2023-30846 is a critical-severity (CVSS 9.1) CWE-522 vulnerability in typed-rest-client. A fix is available for typed-rest-client — see the affected versions and patch details below.
typed-rest-client vulnerable to potential leak of authentication data to 3rd parties
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-30846.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-30846 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
typed-rest-clientnpmDescription
Impact
Users of typed-rest-client library version 1.7.3 or lower are vulnerable to leak authentication data to 3rd parties.
The flow of the vulnerability is as follows:
- Send any request with
BasicCredentialHandler,BearerCredentialHandlerorPersonalAccessTokenCredentialHandler - The target host may return a redirection (3xx), with a link to a second host.
- The next request will use the credentials to authenticate with the second host, by setting the
Authorizationheader.
The expected behavior is that the next request will NOT set the Authorization header.
Patches
The problem was fixed on April 1st 2020.
Workarounds
There is no workaround.
References
This is similar to the following issues in nature:
- HTTP authentication leak in redirects - I used the same solution as CURL did.
- CVE-2018-1000007.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | typed-rest-client | all versions | 1.8.0npm install typed-rest-client@1.8.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typed-rest-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typed-rest-client to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-30846 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-30846 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-30846. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-30846 in your dependencies?
O3 Security finds CVE-2023-30846 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.