CVE-2004-0445
What it is
The SYMDNS.SYS driver in Symantec Norton Internet Security and Professional 2002 through 2004, Norton Personal Firewall 2002 through 2004, Norton AntiSpam 2004, Client Firewall 5.01 and 5.1.1, and Client Security 1.0 through 2.0 allows remote attackers to cause a denial of service (CPU consumption from infinite loop) via a DNS response with a compressed name pointer that points to itself.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 11.0% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 11.0% in the next 30 days (EPSS).
- Severity: 2.6 LOW (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 11.0% · EPSS, next 30 days
- Record status
- Modified
Affected
- Symantec Client Firewall 5.01
- Symantec Client Firewall 5.1.1
- Symantec Client Security 1.0
- Symantec Client Security 1.1
- Symantec Client Security 1.2
- Symantec Client Security 1.3
- Symantec Client Security 1.4
- Symantec Client Security 1.5
Attack profile CVSS 2.0 · 2.6
- Attack vector
- Network
- Complexity
- High
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
Raw vector
AV:N/AC:H/Au:N/C:N/I:N/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2004-0445.md and follow it. Check whether this project is affected by CVE-2004-0445. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://securityresponse.symantec.com/avcenter/security/Content/2004.05.12.html
- http://www.kb.cert.org/vuls/id/682110
- http://securityresponse.symantec.com/avcenter/security/Content/2004.05.12.html
- http://www.kb.cert.org/vuls/id/682110
References
- http://lists.grok.org.uk/pipermail/full-disclosure/2004-May/021359.html
- http://secunia.com/advisories/11066
- http://securityresponse.symantec.com/avcenter/security/Content/2004.05.12.html
- http://securitytracker.com/id?1010144
- http://securitytracker.com/id?1010145
- http://securitytracker.com/id?1010146
- http://www.ciac.org/ciac/bulletins/o-141.shtml
- http://www.kb.cert.org/vuls/id/682110
- http://www.osvdb.org/6100
- http://www.securityfocus.com/bid/10336
- https://exchange.xforce.ibmcloud.com/vulnerabilities/16132
- http://lists.grok.org.uk/pipermail/full-disclosure/2004-May/021359.html
- http://secunia.com/advisories/11066
- http://securityresponse.symantec.com/avcenter/security/Content/2004.05.12.html
- http://securitytracker.com/id?1010144
- http://securitytracker.com/id?1010145
- http://securitytracker.com/id?1010146
- http://www.ciac.org/ciac/bulletins/o-141.shtml
- http://www.kb.cert.org/vuls/id/682110
- http://www.osvdb.org/6100
- http://www.securityfocus.com/bid/10336
- https://exchange.xforce.ibmcloud.com/vulnerabilities/16132