{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-53678 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-53678 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-53678 is a medium-severity SQL injection vulnerability in Apache VCL, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53678 and fix it if it is affected.\n\nWhat it is: CVE-2024-53678 is a medium-severity SQL injection vulnerability in Apache VCL, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-53678 in the wild and no public exploit code.\n\nAffected product: Apache VCL. 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-53678/ (Markdown: https://insights.sbomify.com/CVE-2024-53678/index.md)","id":"CVE-2024-53678","markdown":"https://insights.sbomify.com/CVE-2024-53678/index.md","name":"CVE-2024-53678","record":{"aliases":["GHSA-fwrx-wppx-25wm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Virtual Computing Lab","requires_auth":"high_privilege","summary":"Attackers can modify SQL queries in the New Block Allocation form to potentially access data, though returned data is not directly viewable.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"vcl","vendor":"apache"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/RE:M","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Apache VCL. Users can modify form data submitted when requesting a new Block Allocation such that a SELECT SQL statement is modified. The data returned by the SELECT statement is not viewable by the attacker.\n\nThis issue affects all versions of Apache VCL from 2.2 through 2.5.1.\n\nUsers are recommended to upgrade to version 2.5.2, which fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache VCL: SQL injection vulnerability in New Block Allocation form","id":"CVE-2024-53678","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Apache VCL: XSS vulnerability in User Lookup impacting user privileges","id":"CVE-2024-53679"},"packages":[],"prev":{"headline":"Apache Struts: Mixing setters for uploaded files and normal fields can allow bypass file upload checks","id":"CVE-2024-53677"},"products":["Apache VCL"],"published":"2025-03-25","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2013-0267","kev_date_added":null,"published":"2018-02-21"},{"cvss_score":8.4,"headline":"Apache VCL: XSS vulnerability in User Lookup impacting user privileges","id":"CVE-2024-53679","kev_date_added":null,"published":"2025-03-25"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-31","vendors":["Apache Software Foundation"]},"summary":"Attackers can modify SQL queries in the New Block Allocation form to potentially access data, though returned data is not directly viewable.","url":"https://insights.sbomify.com/CVE-2024-53678/"}