CVE-2006-6017
First published: Tue Nov 21 2006(Updated: )
WordPress before 2.0.5 does not properly store a profile containing a string representation of a serialized object, which allows remote authenticated users to cause a denial of service (application crash) via a string that represents a (1) malformed or (2) large serialized object, because the object triggers automatic unserialization for display.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | <=2.0.5 | |
| <=2.0.5 |
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-2006-6017?
CVE-2006-6017 has a medium severity level due to its potential for causing application crashes.
How do I fix CVE-2006-6017?
The recommended fix for CVE-2006-6017 is to upgrade to WordPress version 2.0.6 or later.
Who is affected by CVE-2006-6017?
CVE-2006-6017 affects all WordPress installations prior to version 2.0.6.
What type of attack does CVE-2006-6017 enable?
CVE-2006-6017 enables denial of service attacks by allowing authenticated users to trigger application crashes with malformed serialized objects.
Can CVE-2006-6017 be exploited remotely?
Yes, CVE-2006-6017 can be exploited by remote authenticated users.
- agent/type
- agent/remedy
- agent/references
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- collector/nvd-historical
- vendor/wordpress
- product/wordpress
- canonical/wordpress wordpress
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/source
- agent/last-modified-date
- agent/weakness
- agent/tags
- collector/nvd-api
- source/NVD
- canonical/wordpress
- version/wordpress/2.0.5