{"answers":{"affected":"2 open source packages ship an affected version, including generator-jhipster-kotlin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-4072 in the wild and no public exploit code.","fix":"Upgrade generator-jhipster-kotlin to 1.7.0 or later.","what":"CVE-2020-4072 is a medium-severity vulnerability in jhipster-kotlin, published on 25 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-4072 and fix it if it is affected.\n\nWhat it is: CVE-2020-4072 is a medium-severity vulnerability in jhipster-kotlin, published on 25 Jun 2020. 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-2020-4072 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- generator-jhipster-kotlin (npm): affected from 1.6.0; fixed in 1.7.0\n- generator-jhipster-kotlin (npm): affected from 1.6.0; fixed in 1.7.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-2020-4072/ (Markdown: https://insights.sbomify.com/CVE-2020-4072/index.md)","id":"CVE-2020-4072","markdown":"https://insights.sbomify.com/CVE-2020-4072/index.md","name":"CVE-2020-4072","record":{"aliases":["GHSA-pfxf-wh96-fvjc"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":true,"product_category":"JHipster Kotlin generator","requires_auth":"none","summary":"Attackers can forge log entries via invalid password reset attempts in JHipster Kotlin generated apps using JWT or session auth.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"generator-jhipster-kotlin","vendor":"jhipster"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"In generator-jhipster-kotlin version 1.6.0 log entries are created for invalid password reset attempts. As the email is provided by a user and the api is public this can be used by an attacker to forge log entries. This is vulnerable to https://cwe.mitre.org/data/definitions/117.html This problem affects only application generated with jwt or session authentication. Applications using oauth are not vulnerable. This issue has been fixed in version 1.7.0.","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":"Log Forging in generator-jhipster-kotlin","id":"CVE-2020-4072","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2020"},"n_packages":2,"n_references":4,"next":{"headline":"Improper Authentication","id":"CVE-2020-4074"},"packages":[{"ecosystem":"npm","fixed":["1.7.0"],"introduced":["1.6.0"],"last_affected":[],"package":"generator-jhipster-kotlin","purl":null,"source":"GHSA-pfxf-wh96-fvjc"},{"ecosystem":"npm","fixed":["1.7.0"],"introduced":["1.6.0"],"last_affected":[],"package":"generator-jhipster-kotlin","purl":"pkg:npm/generator-jhipster-kotlin","source":"GHSA-pfxf-wh96-fvjc"}],"prev":{"headline":"Timing attack on django-basic-auth-ip-whitelist","id":"CVE-2020-4071"},"products":["jhipster-kotlin"],"published":"2020-06-25","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-08-04","vendors":["jhipster"]},"summary":"Attackers can forge log entries via invalid password reset attempts in JHipster Kotlin generated apps using JWT or session auth.","url":"https://insights.sbomify.com/CVE-2020-4072/"}