# CVE-2006-4562: Server-side request forgery in n/a

> Remote attackers can use the proxy DNS service to query third-party servers and hide their source IP, provided the service is enabled on the external interface.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-97wm-hr4h-jwm3

## What is CVE-2006-4562?

CVE-2006-4562 is a medium-severity server-side request forgery vulnerability in n/a, published on 6 Sep 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The proxy DNS service in Symantec Gateway Security (SGS) allows remote attackers to make arbitrary DNS queries to third-party DNS servers, while hiding the source IP address of the attacker.  NOTE: another researcher has stated that the default configuration does not proxy DNS queries received on the external interface

## Which versions are affected by CVE-2006-4562?

It affects 1 product.


Products: Symantec Gateway Security.

## How do I fix CVE-2006-4562?

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

## Is CVE-2006-4562 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4562 and fix it if it is affected.

What it is: CVE-2006-4562 is a medium-severity server-side request forgery vulnerability in n/a, published on 6 Sep 2006. 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-2006-4562 in the wild and no public exploit code.

Affected product: n/a. 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-2006-4562/ (Markdown: https://insights.sbomify.com/CVE-2006-4562/index.md)
```

## Sources

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

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