# CVE-2005-0817: Other in n/a

> Remote attackers can poison the DNS cache in Symantec security appliances to redirect users to malicious sites.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 20 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-73h5-vcc2-gj79

## What is CVE-2005-0817?

CVE-2005-0817 is a medium-severity vulnerability in n/a, published on 20 Mar 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unknown vulnerability in the DNSd proxy, as used in Symantec Gateway Security 5400 2.x and 5300 1.x, Enterprise Firewall 7.0.x and 8.x, and VelociRaptor 1100/1200/1300 1.5, allows remote attackers to poison the DNS cache and redirect users to malicious sites.

## Which versions are affected by CVE-2005-0817?

It affects 4 products.


Products: Symantec Enterprise Firewall, Symantec Gateway Security 5300, Symantec Gateway Security 5400, Symantec Velociraptor.

## How do I fix CVE-2005-0817?

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

## Is CVE-2005-0817 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4422](https://insights.sbomify.com/CVE-2007-4422/): Information disclosure in n/a (critical 9.3)
- [CVE-2005-3768](https://insights.sbomify.com/CVE-2005-3768/): Memory corruption in n/a (high 7.5)
- [CVE-2002-1463](https://insights.sbomify.com/CVE-2002-1463/): Other in n/a (high 7.5)
- [CVE-2002-0538](https://insights.sbomify.com/CVE-2002-0538/): Server-side request forgery in n/a (high 7.5)
- [CVE-2003-0106](https://insights.sbomify.com/CVE-2003-0106/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0817 and fix it if it is affected.

What it is: CVE-2005-0817 is a medium-severity vulnerability in n/a, published on 20 Mar 2005. 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-2005-0817 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-2005-0817/ (Markdown: https://insights.sbomify.com/CVE-2005-0817/index.md)
```

## Sources

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

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