{"answers":{"affected":"2 open source packages ship an affected version, including generator-jhipster. It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-20110 in the wild and no public exploit code.","fix":"Upgrade generator-jhipster to 2.23.0 or later.","what":"CVE-2015-20110 is a high-severity vulnerability in n/a, published on 31 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-20110 and fix it if it is affected.\n\nWhat it is: CVE-2015-20110 is a high-severity vulnerability in n/a, published on 31 Oct 2023. 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-2015-20110 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- generator-jhipster (npm): affected all versions; fixed in 2.23.0\n- generator-jhipster (npm): affected all versions; fixed in 2.23.0\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-2015-20110/ (Markdown: https://insights.sbomify.com/CVE-2015-20110/index.md)","id":"CVE-2015-20110","markdown":"https://insights.sbomify.com/CVE-2015-20110/index.md","name":"CVE-2015-20110","record":{"aliases":["GHSA-4gpm-r23h-gprw"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JHipster generator","requires_auth":"none","summary":"Attackers can bypass token validation in JHipster generator via timing attacks, allowing them to guess valid tokens and potentially access protected resources.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jhipster","vendor":"jhipster"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"JHipster generator-jhipster before 2.23.0 allows a timing attack against validateToken due to a string comparison that stops at the first character that is different. Attackers can guess tokens by brute forcing one character at a time and observing the timing. This of course drastically reduces the search space to a linear amount of guesses based on the token length times the possible characters.","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":"generator-jhipster allows a timing attack against validateToken due to a string comparison that stops at the first character","id":"CVE-2015-20110","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2015"},"n_packages":2,"n_references":4,"next":{"headline":"Memory corruption in n/a","id":"CVE-2015-20111"},"packages":[{"ecosystem":"npm","fixed":["2.23.0"],"introduced":["0"],"last_affected":[],"package":"generator-jhipster","purl":null,"source":"GHSA-4gpm-r23h-gprw"},{"ecosystem":"npm","fixed":["2.23.0"],"introduced":["0"],"last_affected":[],"package":"generator-jhipster","purl":"pkg:npm/generator-jhipster","source":"GHSA-4gpm-r23h-gprw"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2015-20109"},"products":["n/a"],"published":"2023-10-31","related":[{"cvss_score":9.8,"headline":"JHipster Kotlin using insecure source of randomness `RandomStringUtils` before v1.2.0","id":"CVE-2019-16303","kev_date_added":null,"published":"2019-09-13"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-06","vendors":["n/a"]},"summary":"Attackers can bypass token validation in JHipster generator via timing attacks, allowing them to guess valid tokens and potentially access protected resources.","url":"https://insights.sbomify.com/CVE-2015-20110/"}