# CVE-2005-0618: Misconfiguration in n/a

> Attackers can intercept SMTP traffic sent to trusted networks via untrusted networks when load balancing is enabled on Symantec firewalls.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 2 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4m34-p6mv-6g6j

## What is CVE-2005-0618?

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

### Official description

The SMTP binding function in Symantec Firewall/VPN Appliance 200/200R firmware after 1.5Z and before 1.68, Gateway Security 360/360R and 460/460R firmware before vuild 858, and Nexland Pro800turbo, when configured for load balancing between two WANs, might send SMTP traffic to a trusted network through an untrusted network.

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

It affects 4 products.


Products: Nexland Pro800turbo, Symantec Firewall Vpn Appliance 200r, Symantec Gateway Security 360, Symantec Gateway Security 460.

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

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

## Is CVE-2005-0618 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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