CVE-2014-10389

WP Support Plus Responsive Ticket System <= 4.1 - Improper Authentication

2014-11-15 00:00

Strategic Overview

Status: Patched in 4.2
Affected Plugin: WP Support Plus Responsive Ticket System
Affected Version: <= 4.1
CVSS: 9.8Critical
Weakness type: CWE-287 · Improper Authentication
CVE: CVE-2014-10389

View all WP Support Plus Responsive Ticket System vulnerabilities

At a glance

CVE-2014-10389 is a critical-severity Improper Authentication vulnerability in the WP Support Plus Responsive Ticket System WordPress plugin, affecting versions <= 4.1. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.2; sites on affected versions should update now. Disclosed November 2014, reported by Fikri Fadzil.

Vulnerability Overview

The wp-support-plus-responsive-ticket-system plugin before 4.2 for WordPress has incorrect authentication.

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 confidentiality, integrity, availability — full site compromise territory.

CWE-287: Improper Authentication

Reaching this weakness in WP Support Plus Responsive Ticket System <= 4.1 takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For WP Support Plus Responsive Ticket System the fix is 4.2: builds <= 4.1 are affected, anything from 4.2 onward is not.

Remediation

Update to version 4.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Support Plus Responsive Ticket System 4.2 closes this, and updating the plugin is the step that ends it.

Login Security
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2014-10389 https://www.wordfence.com/threat-intel/vulnerabilities/id/3e744c77-efa2-4910-af18-56aa15424412 https://nvd.nist.gov/vuln/detail/CVE-2014-10389

Related records

Other vulnerabilities in WP Support Plus Responsive Ticket System

CVSS Vector

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/