{"answers":{"affected":"2 open source packages ship an affected version, including com.jason-goodwin:authentikat-jwt_2.12. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18239 in the wild and no public exploit code.","fix":"Upgrade com.jason-goodwin:authentikat-jwt_2.12 to 0.4.6 or later.","what":"CVE-2017-18239 is a critical vulnerability in n/a, published on 18 Mar 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-2017-18239 and fix it if it is affected.\n\nWhat it is: CVE-2017-18239 is a critical vulnerability in n/a, published on 18 Mar 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-2017-18239 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.jason-goodwin:authentikat-jwt_2.12 (Maven): affected all versions; fixed in 0.4.6\n- com.jason-goodwin:authentikat-jwt_2.12 (Maven): affected all versions; fixed in 0.4.6\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-2017-18239/ (Markdown: https://insights.sbomify.com/CVE-2017-18239/index.md)","id":"CVE-2017-18239","markdown":"https://insights.sbomify.com/CVE-2017-18239/index.md","name":"CVE-2017-18239","record":{"aliases":["GHSA-3rhm-67j6-42jq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Scala JWT library","requires_auth":"none","summary":"An attacker can bypass JWT signature validation by exploiting a timing side-channel to guess the signature bit-by-bit.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"authentikat-jwt","vendor":"authentikat-jwt_project"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"A time-sensitive equality check on the JWT signature in the JsonWebToken.validate method in main/scala/authentikat/jwt/JsonWebToken.scala in authentikat-jwt (aka com.jason-goodwin/authentikat-jwt) version 0.4.5 and earlier allows the supplier of a JWT token to guess bit after bit of the signature by repeating validation requests.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Exposure of Sensitive information in authentikat-jwt","id":"CVE-2017-18239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":2,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2017-18240"},"packages":[{"ecosystem":"Maven","fixed":["0.4.6"],"introduced":["0"],"last_affected":[],"package":"com.jason-goodwin:authentikat-jwt_2.12","purl":null,"source":"GHSA-3rhm-67j6-42jq"},{"ecosystem":"Maven","fixed":["0.4.6"],"introduced":["0"],"last_affected":[],"package":"com.jason-goodwin:authentikat-jwt_2.12","purl":"pkg:maven/com.jason-goodwin/authentikat-jwt_2.12","source":"GHSA-3rhm-67j6-42jq"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-18238"},"products":["n/a"],"published":"2018-03-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can bypass JWT signature validation by exploiting a timing side-channel to guess the signature bit-by-bit.","url":"https://insights.sbomify.com/CVE-2017-18239/"}