Read the docs
TI-2005-00568 Aliases CVE-2005-0618GHSA-4m34-p6mv-6g6j

The SMTP binding function in Symantec Firewall/VPN Appliance 200/200R firmware after 1.5Z…

Priority LOW 30Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
— Not recorded in CVSS 2.0
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Partial · Partial · None
Fix status
No fix listed

Attack profile from CVSS 2.0 · NVD. Fix status from CNA.

Summary

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.

Why it matters now

EPSS 0.01012 63rd percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
  • — Vendor— Affected all versions Fixed in — No fix listed CNA

CPE configurations NVD · 4

CPEVersionsRoleVendor
cpe:2.3:h:nexland:pro800turbo:*:*:*:*:*:*:*:*all versionsVulnerableNexland
cpe:2.3:h:symantec:firewall_vpn_appliance_200r:*:*:*:*:*:*:*:*all versionsVulnerableSymantec
cpe:2.3:h:symantec:gateway_security_360:*:*:*:*:*:*:*:*up to 857VulnerableSymantec
cpe:2.3:h:symantec:gateway_security_460:*:*:*:*:*:*:*:*up to 857VulnerableSymantec
  • cpe:2.3:h:nexland:pro800turbo:*:*:*:*:*:*:*:* Versions all versions Vulnerable ·Nexland
  • cpe:2.3:h:symantec:firewall_vpn_appliance_200r:*:*:*:*:*:*:*:* Versions all versions Vulnerable ·Symantec
  • cpe:2.3:h:symantec:gateway_security_360:*:*:*:*:*:*:*:* Versions up to 857 Vulnerable ·Symantec
  • cpe:2.3:h:symantec:gateway_security_460:*:*:*:*:*:*:*:* Versions up to 857 Vulnerable ·Symantec

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2005-0618
  2. 2026-10-03 Alias added: GHSA-4m34-p6mv-6g6j

References

Sources