{"answers":{"affected":"2 open source packages ship an affected version, including csrf-lite. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10535 in the wild and no public exploit code.","fix":"Upgrade csrf-lite to 0.1.2 or later.","what":"CVE-2016-10535 is a medium-severity vulnerability in HackerOne csrf-lite node module, published on 31 May 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-2016-10535 and fix it if it is affected.\n\nWhat it is: CVE-2016-10535 is a medium-severity vulnerability in HackerOne csrf-lite node module, published on 31 May 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-2016-10535 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- csrf-lite (npm): affected all versions; fixed in 0.1.2\n- csrf-lite (npm): affected all versions; fixed in 0.1.2\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-2016-10535/ (Markdown: https://insights.sbomify.com/CVE-2016-10535/index.md)","id":"CVE-2016-10535","markdown":"https://insights.sbomify.com/CVE-2016-10535/index.md","name":"CVE-2016-10535","record":{"aliases":["GHSA-hjhr-r3gq-qvp6"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js CSRF library","requires_auth":"none","summary":"An attacker can bypass CSRF protection in csrf-lite by exploiting a timing side-channel to guess the secret token efficiently.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"csrf-lite","vendor":"csrf-lite_project"}],"cvss":{"score":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-310","name":null},{"id":"CWE-208","name":"Observable Timing Discrepancy"}],"description":"csrf-lite is a cross-site request forgery protection library for framework-less node sites. csrf-lite uses `===`, a fail first string comparison, instead of a time constant string comparison This enables an attacker to guess the secret in no more than (16*18)288 guesses, instead of the 16^18 guesses required were the timing attack not present.","ecosystems":["npm"],"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":"Timing Attack in csrf-lite","id":"CVE-2016-10535","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"weak_cryptography","year":"2016"},"n_packages":2,"n_references":2,"next":{"headline":"Insecure Defaults Allow MITM Over TLS in engine.io-client","id":"CVE-2016-10536"},"packages":[{"ecosystem":"npm","fixed":["0.1.2"],"introduced":["0"],"last_affected":[],"package":"csrf-lite","purl":null,"source":"GHSA-hjhr-r3gq-qvp6"},{"ecosystem":"npm","fixed":["0.1.2"],"introduced":["0"],"last_affected":[],"package":"csrf-lite","purl":"pkg:npm/csrf-lite","source":"GHSA-hjhr-r3gq-qvp6"}],"prev":{"headline":"SSL Validation Defaults to False in electron-packager","id":"CVE-2016-10534"},"products":["csrf-lite node module"],"published":"2018-05-31","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":"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-09-17","vendors":["HackerOne"]},"summary":"An attacker can bypass CSRF protection in csrf-lite by exploiting a timing side-channel to guess the secret token efficiently.","url":"https://insights.sbomify.com/CVE-2016-10535/"}