CVE-2022-44581

Defender Security <= 3.3.2 - Sensitive Information Disclosure

2022-11-23 00:00

Strategic Overview

Status: Patched in 3.3.3
Affected Plugin: Defender Security – Malware Scanner, Login Security & Firewall
Affected Version: <= 3.3.2
CVSS: 7.5High
Weakness type: CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE: CVE-2022-44581

View all Defender Security – Malware Scanner, Login Security & Firewall vulnerabilities

At a glance

CVE-2022-44581 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Defender Security WordPress plugin, affecting versions <= 3.3.2. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 3.3.3; sites on affected versions should update now. Disclosed November 2022, reported by Calvin Alkan.

Vulnerability Overview

The Defender Security plugin for WordPress is vulnerable to Sensitive Information Disclosure in versions up to, and including, 3.3.2. This is due to 2fa-codes being stored in plaintext. This makes it possible for unauthenticated attackers to access them under certain circumstances.

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.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Defender Security <= 3.3.2 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Defender Security the fix is 3.3.3: builds <= 3.3.2 are affected, anything from 3.3.3 onward is not.

Remediation

Update to version 3.3.3, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Defender Security 3.3.3 closes this, and updating the plugin is the step that ends it.

Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-44581 https://www.wordfence.com/threat-intel/vulnerabilities/id/662ca451-5c69-4973-afc8-5dc1caf57ad7 https://nvd.nist.gov/vuln/detail/CVE-2022-44581

Related records

Other vulnerabilities in Defender Security – Malware Scanner, Login Security & Firewall

CVSS Vector

7.5

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityNone
AvailabilityNone

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/