CVE-2021-21310 (GCVE-0-2021-21310)
Vulnerability from cvelistv5
Published
2021-02-11 21:40
Modified
2024-08-03 18:09
Severity ?
VLAI Severity ?
EPSS score ?
CWE
- CWE-290 - Authentication Bypass by Spoofing
Summary
NextAuth.js (next-auth) is am open source authentication solution for Next.js applications. In next-auth before version 3.3.0 there is a token verification vulnerability. Implementations using the Prisma database adapter in conjunction with the Email provider are impacted. Implementations using the Email provider with the default database adapter are not impacted. Implementations using the Prisma database adapter but not using the Email provider are not impacted. The Prisma database adapter was checking the verification token, but was not verifying the email address associated with that token. This made it possible to use a valid token to sign in as another user when using the Prima adapter in conjunction with the Email provider. This issue is specific to the community supported Prisma adapter. This issue is fixed in version 3.3.0.
References
▼ | URL | Tags | |
---|---|---|---|
security-advisories@github.com | https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0 | Third Party Advisory | |
security-advisories@github.com | https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q | Exploit, Third Party Advisory | |
security-advisories@github.com | https://www.npmjs.com/package/next-auth | Product, Third Party Advisory | |
af854a3a-2127-422b-91ae-364da2661108 | https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0 | Third Party Advisory | |
af854a3a-2127-422b-91ae-364da2661108 | https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q | Exploit, Third Party Advisory | |
af854a3a-2127-422b-91ae-364da2661108 | https://www.npmjs.com/package/next-auth | Product, Third Party Advisory |
Impacted products
Vendor | Product | Version | ||
---|---|---|---|---|
nextauthjs | next-auth |
Version: < 3.3.0 |
{ "containers": { "adp": [ { "providerMetadata": { "dateUpdated": "2024-08-03T18:09:15.328Z", "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE" }, "references": [ { "tags": [ "x_refsource_CONFIRM", "x_transferred" ], "url": "https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q" }, { "tags": [ "x_refsource_MISC", "x_transferred" ], "url": "https://www.npmjs.com/package/next-auth" }, { "tags": [ "x_refsource_MISC", "x_transferred" ], "url": "https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0" } ], "title": "CVE Program Container" } ], "cna": { "affected": [ { "product": "next-auth", "vendor": "nextauthjs", "versions": [ { "status": "affected", "version": "\u003c 3.3.0" } ] } ], "descriptions": [ { "lang": "en", "value": "NextAuth.js (next-auth) is am open source authentication solution for Next.js applications. In next-auth before version 3.3.0 there is a token verification vulnerability. Implementations using the Prisma database adapter in conjunction with the Email provider are impacted. Implementations using the Email provider with the default database adapter are not impacted. Implementations using the Prisma database adapter but not using the Email provider are not impacted. The Prisma database adapter was checking the verification token, but was not verifying the email address associated with that token. This made it possible to use a valid token to sign in as another user when using the Prima adapter in conjunction with the Email provider. This issue is specific to the community supported Prisma adapter. This issue is fixed in version 3.3.0." } ], "metrics": [ { "cvssV3_1": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.1, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N", "version": "3.1" } } ], "problemTypes": [ { "descriptions": [ { "cweId": "CWE-290", "description": "CWE-290: Authentication Bypass by Spoofing", "lang": "en", "type": "CWE" } ] } ], "providerMetadata": { "dateUpdated": "2021-02-11T21:40:16", "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M" }, "references": [ { "tags": [ "x_refsource_CONFIRM" ], "url": "https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q" }, { "tags": [ "x_refsource_MISC" ], "url": "https://www.npmjs.com/package/next-auth" }, { "tags": [ "x_refsource_MISC" ], "url": "https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0" } ], "source": { "advisory": "GHSA-pg53-56cg-4m8q", "discovery": "UNKNOWN" }, "title": "Token verification bug in next-auth", "x_legacyV4Record": { "CVE_data_meta": { "ASSIGNER": "security-advisories@github.com", "ID": "CVE-2021-21310", "STATE": "PUBLIC", "TITLE": "Token verification bug in next-auth" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "next-auth", "version": { "version_data": [ { "version_value": "\u003c 3.3.0" } ] } } ] }, "vendor_name": "nextauthjs" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "NextAuth.js (next-auth) is am open source authentication solution for Next.js applications. In next-auth before version 3.3.0 there is a token verification vulnerability. Implementations using the Prisma database adapter in conjunction with the Email provider are impacted. Implementations using the Email provider with the default database adapter are not impacted. Implementations using the Prisma database adapter but not using the Email provider are not impacted. The Prisma database adapter was checking the verification token, but was not verifying the email address associated with that token. This made it possible to use a valid token to sign in as another user when using the Prima adapter in conjunction with the Email provider. This issue is specific to the community supported Prisma adapter. This issue is fixed in version 3.3.0." } ] }, "impact": { "cvss": { "attackComplexity": "HIGH", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.1, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "CHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N", "version": "3.1" } }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "CWE-290: Authentication Bypass by Spoofing" } ] } ] }, "references": { "reference_data": [ { "name": "https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q", "refsource": "CONFIRM", "url": "https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q" }, { "name": "https://www.npmjs.com/package/next-auth", "refsource": "MISC", "url": "https://www.npmjs.com/package/next-auth" }, { "name": "https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0", "refsource": "MISC", "url": "https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0" } ] }, "source": { "advisory": "GHSA-pg53-56cg-4m8q", "discovery": "UNKNOWN" } } } }, "cveMetadata": { "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "assignerShortName": "GitHub_M", "cveId": "CVE-2021-21310", "datePublished": "2021-02-11T21:40:16", "dateReserved": "2020-12-22T00:00:00", "dateUpdated": "2024-08-03T18:09:15.328Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "vulnerability-lookup:meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2021-21310\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2021-02-11T22:15:12.507\",\"lastModified\":\"2024-11-21T05:47:59.690\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"NextAuth.js (next-auth) is am open source authentication solution for Next.js applications. In next-auth before version 3.3.0 there is a token verification vulnerability. Implementations using the Prisma database adapter in conjunction with the Email provider are impacted. Implementations using the Email provider with the default database adapter are not impacted. Implementations using the Prisma database adapter but not using the Email provider are not impacted. The Prisma database adapter was checking the verification token, but was not verifying the email address associated with that token. This made it possible to use a valid token to sign in as another user when using the Prima adapter in conjunction with the Email provider. This issue is specific to the community supported Prisma adapter. This issue is fixed in version 3.3.0.\"},{\"lang\":\"es\",\"value\":\"NextAuth.js (next-auth) es una soluci\u00f3n de autenticaci\u00f3n de c\u00f3digo abierto para aplicaciones Next.js.\u0026#xa0;En next-auth versiones anteriores a 3.3.0, se presenta una vulnerabilidad de verificaci\u00f3n de tokens.\u0026#xa0;Las implementaciones que usa el adaptador de base de datos Prisma en conjunto con el proveedor de correo electr\u00f3nico est\u00e1n afectadas.\u0026#xa0;Las implementaciones que usa el proveedor de correo electr\u00f3nico con el adaptador de base de datos predeterminado no est\u00e1n afectadas.\u0026#xa0;Las implementaciones que usa el adaptador de base de datos Prisma pero que no usa el proveedor de correo electr\u00f3nico no est\u00e1n afectadas.\u0026#xa0;El adaptador de base de datos de Prisma estaba comprobando el token de verificaci\u00f3n, pero no verificaba la direcci\u00f3n de correo electr\u00f3nico asociada con ese token.\u0026#xa0;Esto hizo posible usar un token v\u00e1lido para iniciar sesi\u00f3n como otro usuario cuando se usa el adaptador Prima en conjunto con el proveedor de correo electr\u00f3nico.\u0026#xa0;Este problema es espec\u00edfico del adaptador Prisma compatible con la comunidad.\u0026#xa0;Este problema es corregido en versi\u00f3n 3.3.0\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N\",\"baseScore\":6.1,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"REQUIRED\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":1.6,\"impactScore\":4.0},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N\",\"baseScore\":5.9,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.2,\"impactScore\":3.6}],\"cvssMetricV2\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"2.0\",\"vectorString\":\"AV:N/AC:M/Au:N/C:P/I:N/A:N\",\"baseScore\":4.3,\"accessVector\":\"NETWORK\",\"accessComplexity\":\"MEDIUM\",\"authentication\":\"NONE\",\"confidentialityImpact\":\"PARTIAL\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"baseSeverity\":\"MEDIUM\",\"exploitabilityScore\":8.6,\"impactScore\":2.9,\"acInsufInfo\":false,\"obtainAllPrivilege\":false,\"obtainUserPrivilege\":false,\"obtainOtherPrivilege\":false,\"userInteractionRequired\":false}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-290\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:nextauth.js:next-auth:*:*:*:*:*:node.js:*:*\",\"versionEndExcluding\":\"3.3.0\",\"matchCriteriaId\":\"33AEB592-BAC1-4FE4-84E0-C8F9E95BF8E5\"}]}]}],\"references\":[{\"url\":\"https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]},{\"url\":\"https://www.npmjs.com/package/next-auth\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Product\",\"Third Party Advisory\"]},{\"url\":\"https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Third Party Advisory\"]},{\"url\":\"https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Exploit\",\"Third Party Advisory\"]},{\"url\":\"https://www.npmjs.com/package/next-auth\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Product\",\"Third Party Advisory\"]}]}}" } }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…