Passport Oauth2
Approved changes feed: RSS · Atom
cpe:2.3:a:passportjs:passport-oauth2:*:*:*:*:*:node.js:*:*part: a version: * update: *
| Vendor | Passportjs (957242c6-3032-5d25-adc4-5abbdb16ca5b) |
|---|---|
| Product | Passport Oauth2 (1eb96090-eb3d-5acb-97e3-5dc4698c5d9a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-41580 |
vulnerable | 2026-06-08 05:35:20.763631 |
Details available
The passport-oauth2 package before 1.6.1 for Node.js mishandles the error condition of failure to obtain an access token. This is exploitable in certain use cases where an OAuth identity provider uses an HTTP 200 status code for authentication-failure error reports, and an application grants authorization upon simply receiving the access token (i.e., does not try to use the token). NOTE: the passport-oauth2 vendor does not consider this a passport-oauth2 vulnerability
Published: 2021-09-27T06:11:20.000Z
Updated: 2024-08-04T03:15:29.285Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.