CVE-2016-4029: SSRF
First published: Sun Aug 07 2016(Updated: )
WordPress before 4.5 does not consider octal and hexadecimal IP address formats when determining an intranet address, which allows remote attackers to bypass an intended SSRF protection mechanism via a crafted address.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WordPress | <=4.4.4 | |
| WordPress | <4.5 | |
| Debian GNU/Linux | =8.0 |
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-2016-4029?
CVE-2016-4029 has a medium severity due to its potential for SSRF attacks.
How do I fix CVE-2016-4029?
To fix CVE-2016-4029, upgrade your WordPress installation to version 4.5 or higher.
Which versions of WordPress are affected by CVE-2016-4029?
CVE-2016-4029 affects WordPress versions prior to 4.5.
Can CVE-2016-4029 be exploited remotely?
Yes, CVE-2016-4029 can be exploited remotely, allowing attackers to bypass SSRF protections.
What types of addresses does CVE-2016-4029 affect?
CVE-2016-4029 affects octal and hexadecimal IP address formats.
- agent/type
- agent/severity
- agent/references
- agent/author
- agent/remedy
- agent/description
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/tags
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- vendor/wordpress
- canonical/wordpress
- version/wordpress/4.4.4
- vendor/debian
- canonical/debian gnu/linux
- version/debian gnu/linux/8.0