{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-16983 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16983 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16983 is a critical vulnerability in n/a, published on 13 Sep 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-16983 and fix it if it is affected.\n\nWhat it is: CVE-2018-16983 is a critical vulnerability in n/a, published on 13 Sep 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-16983 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-16983/ (Markdown: https://insights.sbomify.com/CVE-2018-16983/index.md)","id":"CVE-2018-16983","markdown":"https://insights.sbomify.com/CVE-2018-16983/index.md","name":"CVE-2018-16983","record":{"aliases":["GHSA-v8jx-7m24-m4pm"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"NoScript browser extension","requires_auth":"none","summary":"Attackers can bypass NoScript script blocking protections by using a specific Content-Type header, potentially allowing malicious scripts to execute.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"noscript","vendor":"noscript"},{"product":"tor_browser","vendor":"torproject"}],"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":"NoScript Classic before 5.1.8.7, as used in Tor Browser 7.x and other products, allows attackers to bypass script blocking via the text/html;/json Content-Type value.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2018-16983","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Django allows unprivileged users to read the password hashes of arbitrary accounts","id":"CVE-2018-16984"},"packages":[],"prev":{"headline":"Open Chinese Convert subject to Denial of Service via Out-of-bounds Read","id":"CVE-2018-16982"},"products":["n/a"],"published":"2018-09-13","related":[],"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":"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 bypass NoScript script blocking protections by using a specific Content-Type header, potentially allowing malicious scripts to execute.","url":"https://insights.sbomify.com/CVE-2018-16983/"}