{"answers":{"affected":"It affects 3 products.","exploited":"Yes. Attackers have exploited CVE-2024-0519 in the wild since at least 17 Jan 2024.","fix":"Upgrade to a fixed version. US federal agencies must fix it by 7 Feb 2024.","what":"CVE-2024-0519 is a high-severity memory corruption vulnerability in Couchbase Couchbase Server, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-0519 and fix it if it is affected.\n\nWhat it is: CVE-2024-0519 is a high-severity memory corruption vulnerability in Couchbase Couchbase Server, published on 16 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: Yes. Attackers have exploited CVE-2024-0519 in the wild since at least 17 Jan 2024.\n\nAffected product: Couchbase Couchbase Server. 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-2024-0519/ (Markdown: https://insights.sbomify.com/CVE-2024-0519/index.md)","id":"CVE-2024-0519","markdown":"https://insights.sbomify.com/CVE-2024-0519/index.md","name":"CVE-2024-0519","record":{"aliases":["DEBIAN-CVE-2024-0519","GHSA-vg6w-jr5m-86c8"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome","requires_auth":"none","summary":"Remote attackers can exploit heap corruption in Chrome's V8 engine via crafted HTML pages, potentially executing arbitrary code.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"couchbase_server","vendor":"couchbase"},{"product":"fedora","vendor":"fedoraproject"},{"product":"chrome","vendor":"google"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Out of bounds memory access in V8 in Google Chrome prior to 120.0.6099.224 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-05-16","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-05-16T12:43:21Z","kind":"github_poc","ref":"https://github.com/Insaida/cve-2024-0519-rca-research","stars":0,"title":"CVE-2024-0519 root cause analysis "}],"tier":"exploited"},"has_fix":true,"headline":"Google Chromium V8 Out-of-Bounds Memory Access","id":"CVE-2024-0519","indexable":true,"kev":{"dateAdded":"2024-01-17","dueDate":"2024-02-07","knownRansomwareCampaignUse":"Unknown","product":"Chromium V8","requiredAction":"Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.","vendorProject":"Google","vulnerabilityName":"Google Chromium V8 Out-of-Bounds Memory Access Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"couchbase:couchbase_server","products":["couchbase:couchbase_server","fedoraproject:fedora","google:chrome"],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":5,"next":{"headline":"Remote Code Execution due to Full Controlled File Write in mlflow/mlflow","id":"CVE-2024-0520"},"packages":[],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2024-0518"},"products":["Chrome"],"published":"2024-01-16","related":[{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2023-3079","kev_date_added":"2023-06-07","published":"2023-06-05"},{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2023-2033","kev_date_added":"2023-04-17","published":"2023-04-14"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-49930","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-49931","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-35943","kev_date_added":null,"published":"2021-09-29"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2020-24719","kev_date_added":null,"published":"2020-11-12"}],"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"active","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-21","vendors":["Google"]},"summary":"Remote attackers can exploit heap corruption in Chrome's V8 engine via crafted HTML pages, potentially executing arbitrary code.","url":"https://insights.sbomify.com/CVE-2024-0519/"}