{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-2243 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-2243 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2243 is a medium-severity server-side request forgery vulnerability in Bitdefender GravityZone Console, published on 4 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-2243 and fix it if it is affected.\n\nWhat it is: CVE-2025-2243 is a medium-severity server-side request forgery vulnerability in Bitdefender GravityZone Console, published on 4 Apr 2025. 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-2025-2243 in the wild and no public exploit code.\n\nAffected product: Bitdefender GravityZone Console. 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-2025-2243/ (Markdown: https://insights.sbomify.com/CVE-2025-2243/index.md)","id":"CVE-2025-2243","markdown":"https://insights.sbomify.com/CVE-2025-2243/index.md","name":"CVE-2025-2243","record":{"aliases":["GHSA-gh58-477c-r78w"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GravityZone Console","requires_auth":"none","summary":"An attacker can bypass input validation via DNS truncation to perform server-side request forgery, potentially leading to third-party code execution.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Bitdefender","cpe":[{"product":"gravityzone","vendor":"bitdefender"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A server-side request forgery (SSRF) vulnerability in Bitdefender GravityZone Console allows an attacker to bypass input validation logic using leading characters in DNS requests. Paired with other potential vulnerabilities, this bypass could be used for execution of third party code. This issue affects GravityZone Console: before 6.41.2.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SSRF in GravityZone Console via DNS Truncation (VA-12634)","id":"CVE-2025-2243","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Insecure PHP deserialization issue in GravityZone Console (VA-12634)","id":"CVE-2025-2244"},"packages":[],"prev":{"headline":"Incorrect Authorization in GitLab","id":"CVE-2025-2242"},"products":["GravityZone Console"],"published":"2025-04-04","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-8931","kev_date_added":null,"published":"2018-10-30"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2018-8955","kev_date_added":null,"published":"2018-10-24"},{"cvss_score":9.5,"headline":"Insecure PHP deserialization issue in GravityZone Console (VA-12634)","id":"CVE-2025-2244","kev_date_added":null,"published":"2025-04-04"},{"cvss_score":9.2,"headline":"Verbose error handling issue in GravityZone Update Server proxy service","id":"CVE-2024-6980","kev_date_added":null,"published":"2024-07-31"},{"cvss_score":8.8,"headline":"Deserialization of Untrusted Data in GravityZone Console On-Premise (VA-10573)","id":"CVE-2022-2830","kev_date_added":null,"published":"2022-09-05"},{"cvss_score":8.1,"headline":"Host whitelist parser issue in GravityZone Console On-Premise (VA-11554)","id":"CVE-2024-4177","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":7.1,"headline":"Privilege Escalation via the GravityZone productManager UpdateServer.KitsManager API (VA-10146)","id":"CVE-2021-3960","kev_date_added":null,"published":"2021-12-16"}],"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":"2025-04-04","vendors":["Bitdefender"]},"summary":"An attacker can bypass input validation via DNS truncation to perform server-side request forgery, potentially leading to third-party code execution.","url":"https://insights.sbomify.com/CVE-2025-2243/"}