CVE-2022-44589

miniOrange's Google Authenticator <= 5.6.1 - Sensitive Data Exposure of Multifactor Backup Codes

2022-11-23 00:00
Calvin Alkan

Strategic Overview

Status
Patched in 5.6.2
Affected Version
<= 5.6.1
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2022-44589
View all miniOrange 2FA – Two Factor Authentication for WordPress (OTP, SMS, Email, Google Authenticator) vulnerabilities

At a glance

CVE-2022-44589 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the miniOrange 2FA WordPress plugin, affecting versions <= 5.6.1. 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 5.6.2; sites on affected versions should update now. Disclosed November 2022, reported by Calvin Alkan.

Vulnerability Overview

The miniOrange's Google Authenticator plugin for WordPress is vulnerable to Sensitive Data Exposure in versions up to, and including, 5.6.1 via functions such as 'mo_wpns_get_progress' and 'mo2f_use_backup_codes'. This can allow attackers to extract sensitive data about multifactor authentication backup codes, and information about plugin malware scans.

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

miniOrange 2FA <= 5.6.1 carries this weakness at mo_wpns_get_progress, and reaching it 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 miniOrange 2FA the fix is 5.6.2: builds <= 5.6.1 are affected, anything from 5.6.2 onward is not.

Remediation

Update to version 5.6.2, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: miniOrange 2FA 5.6.2 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