{"cve": [{"lastseen": "2022-03-23T18:30:53", "description": "CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.", "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 8.8, "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "version": "3.0", "userInteraction": "REQUIRED"}, "impactScore": 5.9}, "published": "2018-04-04T17:29:00", "type": "cve", "title": "CVE-2018-6874", "cwe": ["CWE-352"], "bulletinFamily": "NVD", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 8.6, "obtainAllPrivilege": false, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 6.8, "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 6.4, "obtainUserPrivilege": false}, "cvelist": ["CVE-2018-6874"], "modified": "2018-05-15T18:08:00", "cpe": ["cpe:/a:auth0:auth0.js:8.12.1"], "id": "CVE-2018-6874", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-6874", "cvss": {"score": 6.8, "vector": "AV:N/AC:M/Au:N/C:P/I:P/A:P"}, "cpe23": ["cpe:2.3:a:auth0:auth0.js:8.12.1:*:*:*:*:*:*:*"]}], "osv": [{"lastseen": "2022-05-11T21:40:54", "description": "CSRF exists in the Auth0 authentication service through 14591 if the Legacy Lock API flag is enabled.", "cvss3": {"exploitabilityScore": 2.8, "cvssV3": {"baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 8.8, "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "version": "3.0", "userInteraction": "REQUIRED"}, "impactScore": 5.9}, "published": "2018-11-06T23:15:13", "type": "osv", "title": "Moderate severity vulnerability that affects auth0-js", "bulletinFamily": "software", "cvss2": {"severity": "MEDIUM", "exploitabilityScore": 8.6, "obtainAllPrivilege": false, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "MEDIUM", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 6.8, "vectorString": "AV:N/AC:M/Au:N/C:P/I:P/A:P", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 6.4, "obtainUserPrivilege": false}, "cvelist": ["CVE-2018-6874"], "modified": "2021-09-21T21:53:18", "id": "OSV:GHSA-WV26-RJ8C-4R33", "href": "https://osv.dev/vulnerability/GHSA-wv26-rj8c-4r33", "cvss": {"score": 6.8, "vector": "AV:N/AC:M/Au:N/C:P/I:P/A:P"}}], "thn": [{"lastseen": "2022-05-09T12:40:37", "description": "[](<https://thehackernews.com/images/-c1hjF3SF8_k/WsiJ67GBlyI/AAAAAAAAwIY/J4Tp5y0XFV8usA2szm5NCXTQ6VU1brvdgCLcBGAs/s728-e100/auth0-authentication-vulnerability.png>)\n\nA critical authentication bypass vulnerability has been discovered in one of the biggest identity-as-a-service platform** Auth0** that could have allowed a malicious attacker to access any portal or application, which are using Auth0 service for authentication. \n \nAuth0 offers token-based authentication solutions for a number of platforms including the ability to integrate social media authentication into an application. \n \nWith over 2000 enterprise customers and managing 42 million logins every day and billions of login per month, Auth0 is one of the biggest identity platforms. \n \nWhile pentesting an application back in September 2017, researchers from security firm Cinta Infinita [discovered](<https://medium.com/@cintainfinita/knocking-down-the-big-door-8e2177f76ea5>) a flaw ([CVE-2018-6873](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6873>)) in Auth0's **Legacy Lock API**, which resides due to improper validation of the JSON Web Tokens (JWT) audience parameter. \n \nResearchers successfully exploited this issue to bypass login authentication using a simple cross-site request forgery (CSRF/XSRF) attack against the applications running over Auth0 authentication. \n \nAuth0's CSRF vulnerability ([CVE-2018-6874](<https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6874>)) allows an attacker to reuse a valid signed JWT generated for a separate account to access the targeted victim's account. \n \nFor this, all an attacker needs is the victim's user ID or email address, which can be obtained using simple social engineering tricks. \n \n\n\n### Video Demonstration of the Attack\n\nAccording to the researchers, the attack is reproducible against many organisations, \"as long as we know the expected fields and values for the JWT. There is no need of social engineering in most of the cases we saw. Authentication for applications that use an email address or an incremental integer for user identification would be trivially bypassed.\" \n \nThe security firm reported the vulnerability to the Auth0 Security Team in October 2017. The company acted very fast and addressed the weakness in less than 4 hours. \n \nHowever, since the vulnerable SDK and supported libraries of Auth0 have been implemented on the client side, Auth0 took almost six months to contact each of their customers and help them fix this vulnerability, before publicly disclosing this issue. \n\n\n> \"Unlike the fix for the special case discovered by Cinta Infinita, this issue could not be solved without forcing our customers to upgrade the libraries/SDKs on their end, a much more significant undertaking,\" the Auth0 team said in its [advisory](<https://auth0.com/blog/managing-and-mitigating-security-vulnerabilities-at-auth0/>).\n\nThe company has mitigated the vulnerabilities by extensively rewriting the affected libraries and releasing new versions of its SDKs (auth0.js 9 and Lock 11). \n \nCinta Infinita also waited six months before publicly disclosing the vulnerability, giving the Auth0 team enough time to update all their Private SaaS Appliances (on-premises) as well. \n \nThe security firm has now released a proof-of-concept (PoC) video, demonstrating how they obtained the victim's user id and bypass password authentication when logging into Auth0's Management Dashboard by forging an authentication token.\n", "cvss3": {"exploitabilityScore": 3.9, "cvssV3": {"baseSeverity": "CRITICAL", "confidentialityImpact": "HIGH", "attackComplexity": "LOW", "scope": "UNCHANGED", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "baseScore": 9.8, "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "version": "3.0", "userInteraction": "NONE"}, "impactScore": 5.9}, "published": "2018-04-07T09:08:00", "type": "thn", "title": "Authentication Bypass Vulnerability Found in Auth0 Identity Platform", "bulletinFamily": "info", "cvss2": {"severity": "HIGH", "exploitabilityScore": 10.0, "obtainAllPrivilege": false, "userInteractionRequired": false, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "LOW", "confidentialityImpact": "PARTIAL", "availabilityImpact": "PARTIAL", "integrityImpact": "PARTIAL", "baseScore": 7.5, "vectorString": "AV:N/AC:L/Au:N/C:P/I:P/A:P", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 6.4, "acInsufInfo": true, "obtainUserPrivilege": false}, "cvelist": ["CVE-2018-6873", "CVE-2018-6874"], "modified": "2018-04-09T18:01:41", "id": "THN:00180D45F9D5175BE38C6A5629CD9B8E", "href": "https://thehackernews.com/2018/04/auth0-authentication-bypass.html", "cvss": {"score": 7.5, "vector": "AV:N/AC:L/Au:N/C:P/I:P/A:P"}}]}
Moderate severity vulnerability that affects auth0-js
