{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-13420 in the wild and no public exploit code.","fix":"No fix published yet.","what":"CVE-2018-13420 is a high-severity denial of service vulnerability in n/a, published on 7 Jul 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-13420 and fix it if it is affected.\n\nWhat it is: CVE-2018-13420 is a high-severity denial of service vulnerability in n/a, published on 7 Jul 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-13420 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-13420/ (Markdown: https://insights.sbomify.com/CVE-2018-13420/index.md)","id":"CVE-2018-13420","markdown":"https://insights.sbomify.com/CVE-2018-13420/index.md","name":"CVE-2018-13420","record":{"aliases":["AZL-6453","DEBIAN-CVE-2018-13420","GHSA-jc8c-gg53-wcm7","UBUNTU-CVE-2018-13420"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"gperftools memory allocator","requires_auth":"none","summary":"A reported memory leak in gperftools could theoretically lead to resource exhaustion, though maintainers dispute this as a false positive.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gperftools","vendor":"gperftools_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"}],"description":"Google gperftools 2.7 has a memory leak in malloc_extension.cc, related to MallocExtension::Register and InitModule. NOTE: the software maintainer indicates that this is not a bug; it is only a false-positive report from the LeakSanitizer program","ecosystems":[],"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":"Denial of service in n/a","id":"CVE-2018-13420","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-13421"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-13419"},"products":["n/a"],"published":"2018-07-07","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":"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-11-14","vendors":["n/a"]},"summary":"A reported memory leak in gperftools could theoretically lead to resource exhaustion, though maintainers dispute this as a false positive.","url":"https://insights.sbomify.com/CVE-2018-13420/"}