{"answers":{"affected":"2 open source packages ship an affected version, including json-jwt. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000539 in the wild and no public exploit code.","fix":"Upgrade json-jwt to 1.9.4 or later.","what":"CVE-2018-1000539 is a medium-severity 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-1000539 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000539 is a medium-severity 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-1000539 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- json-jwt (RubyGems): affected from 0.5.1; fixed in 1.9.4\n- json-jwt (RubyGems): affected from 0.5.1; fixed in 1.9.4\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-1000539/ (Markdown: https://insights.sbomify.com/CVE-2018-1000539/index.md)","id":"CVE-2018-1000539","markdown":"https://insights.sbomify.com/CVE-2018-1000539/index.md","name":"CVE-2018-1000539","record":{"aliases":["CVE-2018-3768","DEBIAN-CVE-2018-1000539","DSA-4283-1","GHSA-mj4x-wcxf-hm8x","UBUNTU-CVE-2018-1000539"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby JWT library","requires_auth":"none","summary":"Attackers can forge authentication tags in AES-GCM encrypted JSON Web Tokens, bypassing signature verification in the json-jwt Ruby library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"json-jwt","vendor":"json-jwt_project"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Nov json-jwt version \u003e= 0.5.0 \u0026\u0026 \u003c 1.9.4 contains a CWE-347: Improper Verification of Cryptographic Signature vulnerability in Decryption of AES-GCM encrypted JSON Web Tokens that can result in Attacker can forge a authentication tag. This attack appear to be exploitable via network connectivity. This vulnerability appears to have been fixed in 1.9.4 and later.","ecosystems":["RubyGems"],"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":"Json-jwt did not verify the cryptographic signature for data","id":"CVE-2018-1000539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":2,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2018-1000540"},"packages":[{"ecosystem":"RubyGems","fixed":["1.9.4"],"introduced":["0.5.1"],"last_affected":[],"package":"json-jwt","purl":null,"source":"GHSA-mj4x-wcxf-hm8x"},{"ecosystem":"RubyGems","fixed":["1.9.4"],"introduced":["0.5.1"],"last_affected":[],"package":"json-jwt","purl":"pkg:gem/json-jwt","source":"GHSA-mj4x-wcxf-hm8x"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-1000538"},"products":["n/a"],"published":"2018-06-26","related":[{"cvss_score":8.4,"headline":"json-jwt allows bypass of identity checks via a sign/encryption confusion attack","id":"CVE-2023-51774","kev_date_added":null,"published":"2023-12-25"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Attackers can forge authentication tags in AES-GCM encrypted JSON Web Tokens, bypassing signature verification in the json-jwt Ruby library.","url":"https://insights.sbomify.com/CVE-2018-1000539/"}