@acastellon/auth has an authentication bypass via spoofable headers in validateToken()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| antonio-castellon | module-auth | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Antonio-castellon | Module-auth |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-gfj5-979r-92pw | @acastellon/auth: Authentication bypass via spoofable headers in validateToken() |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.973% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Antonio-castellon
Antonio-castellon module-auth |
|
| Vendors & Products |
Antonio-castellon
Antonio-castellon module-auth |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | @acastellon/auth is an authentication control system for microservices. Versions prior to 2.3.0 appear to allow an unauthenticated authentication bypass in validateToken() through spoofable auth-user and Host request headers. The validateToken middleware contains a service-to-service bypass for auth-user: service-brother when req.get('host').startsWith(getHostName()). Both values involved in the check can be influenced by an unauthenticated HTTP client: auth-user is a request header, and Host is also client-controlled. As a result, a remote unauthenticated attacker can send a request with crafted headers and bypass token validation before the normal legacy/JWT/OIDC validation logic runs. A fix has been implemented in v2.3.0. | |
| Title | @acastellon/auth has an authentication bypass via spoofable headers in validateToken() | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV4_0
|