{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000531 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1000531 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1000531 is a high-severity authentication bypass vulnerability in n/a, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000531 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000531 is a high-severity authentication bypass vulnerability in n/a, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1000531 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-1000531/ (Markdown: https://insights.sbomify.com/CVE-2018-1000531/index.md)","id":"CVE-2018-1000531","markdown":"https://insights.sbomify.com/CVE-2018-1000531/index.md","name":"CVE-2018-1000531","record":{"aliases":["GHSA-jc5h-g7j7-qh2w"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java JWT library","requires_auth":"none","summary":"Attackers can bypass JWT signature validation by using the 'none' algorithm, allowing unauthorized access in applications using this library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"prime-jwt","vendor":"inversoft"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"inversoft prime-jwt version prior to commit abb0d479389a2509f939452a6767dc424bb5e6ba contains a CWE-20 vulnerability in JWTDecoder.decode that can result in an incorrect signature validation of a JWT token. This attack can be exploitable when an attacker crafts a JWT token with a valid header using 'none' as algorithm and a body to requests it be validated. This vulnerability was fixed after commit abb0d479389a2509f939452a6767dc424bb5e6ba.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2024-11-15","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2024-11-15T21:00:24Z","kind":"github_poc","ref":"https://github.com/realbatuhan/JWT-Bruteforcer","stars":1,"title":"Jwt Bruteforcer with CVE-2018-1000531 Test"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Auth bypass in n/a","id":"CVE-2018-1000531","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2018-1000532"},"packages":[],"prev":{"headline":"Stored Cross Site Scripting in Grails Fields Plugin","id":"CVE-2018-1000529"},"products":["n/a"],"published":"2018-06-26","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2018-1000125","kev_date_added":null,"published":"2018-03-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass JWT signature validation by using the 'none' algorithm, allowing unauthorized access in applications using this library.","url":"https://insights.sbomify.com/CVE-2018-1000531/"}