CVE-2005-3899
First published: Tue Nov 29 2005(Updated: )
The automatic update feature in Google Talk allows remote attackers to cause a denial of service (CPU and memory consumption) by poisoning a target's DNS cache and causing a large update file to be sent, which consumes large amounts of CPU and memory during the signature verification, aka BenjiBug.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Talk Plugin |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2005-3899?
The severity of CVE-2005-3899 is high due to its ability to cause denial of service through excessive CPU and memory consumption.
How do I fix CVE-2005-3899?
To fix CVE-2005-3899, you should disable the automatic update feature in Google Talk and monitor for any suspicious DNS behavior.
What type of attack is described by CVE-2005-3899?
CVE-2005-3899 describes a denial of service attack that targets Google Talk via DNS cache poisoning.
What software is affected by CVE-2005-3899?
CVE-2005-3899 affects all versions of Google Talk that utilize its automatic update feature.
What can be done to mitigate CVE-2005-3899?
To mitigate CVE-2005-3899, users should implement DNSSEC to secure against DNS spoofing and monitor network traffic for anomalies.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/references
- agent/weakness
- agent/last-modified-date
- agent/severity
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/google
- canonical/google talk plugin