CVE-2015-9345

Link Log – external link click monitor <= 1.4 - HTTP Response Splitting

2015-04-28 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0
Affected Version
<= 1.4
CVSS
7.5High
Weakness type
CWE-113 · Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
CVE
CVE-2015-9345
View all Smart External Link Click Monitor [Link Log] vulnerabilities

At a glance

CVE-2015-9345 is a high-severity Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in the Smart External Link Click Monitor [Link Log] WordPress plugin, affecting versions <= 1.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 2.0; sites on affected versions should update now. Disclosed April 2015.

Vulnerability Overview

The Link Log plugin for WordPress is vulnerable to HTTP Response Splitting in versions up to, and including 1.4. This is due to improper input validation. This makes it possible for unauthenticated attackers to perform various other future attacks such as XSS, Cross-User Defacement, Web Cache Poisoning, etc.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.

Remediation

Update to version 2.0, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Smart External Link Click Monitor [Link Log] 2.0 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C