# CVE-2025-2243: SSRF in GravityZone Console via DNS Truncation (VA-12634)

> An attacker can bypass input validation via DNS truncation to perform server-side request forgery, potentially leading to third-party code execution.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-gh58-477c-r78w

## What is CVE-2025-2243?

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.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-2243?

It affects 1 product.


Products: Bitdefender Gravityzone.

## How do I fix CVE-2025-2243?

No fix has been published for CVE-2025-2243 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2243 being exploited?

There is no known exploitation of CVE-2025-2243 in the wild and no public exploit code.

## Other vulnerabilities in Bitdefender GravityZone Console

- [CVE-2017-8931](https://insights.sbomify.com/CVE-2017-8931/): Privilege escalation in n/a (critical 9.8)
- [CVE-2018-8955](https://insights.sbomify.com/CVE-2018-8955/): Code injection in n/a (critical 9.8)
- [CVE-2025-2244](https://insights.sbomify.com/CVE-2025-2244/): Insecure PHP deserialization issue in GravityZone Console (VA-12634) (critical 9.5)
- [CVE-2024-6980](https://insights.sbomify.com/CVE-2024-6980/): Verbose error handling issue in GravityZone Update Server proxy service (critical 9.2)
- [CVE-2022-2830](https://insights.sbomify.com/CVE-2022-2830/): Deserialization of Untrusted Data in GravityZone Console On-Premise (VA-10573) (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2243 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2025-2243 in the wild and no public exploit code.

Affected product: Bitdefender GravityZone Console. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2243/ (Markdown: https://insights.sbomify.com/CVE-2025-2243/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2243
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2243
- OSV: https://osv.dev/vulnerability/CVE-2025-2243

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2243/
Summaries are generated and may contain mistakes; the official description above is the record.