Security Resilience

CVE-2024-12108

Auth Bypass in Progress Whatsup Gold 23.1.0 – 24.0.2

Published
31 December 2024
Modified
06 January 2025
Patch / advisory
CVSS Score v3.1 9.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS Score 0.077 95th percentile
Risk Priority 79 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-12108 is a critical-severity Authentication Bypass by Spoofing (CWE-290) vulnerability in Progress Whatsup Gold. Its CVSS base score is 9.6 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-2 (Identification and Authentication (Organizational Users)) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The vulnerability CVE-2024-12108 affects WhatsUp Gold versions released before 2024.0.2. It enables an attacker to gain access to the WhatsUp Gold server via the public API and is associated with CWE-290. The issue received a CVSS 3.1 score of 9.6 reflecting network attack vector, low complexity, low required privileges, and changed scope with high confidentiality and integrity impact.

An attacker positioned on the network and holding only low privileges can exploit the flaw without user interaction to obtain unauthorized access to the server and perform high-impact actions on confidentiality and integrity.

The vendor Progress Software lists related network monitoring resources at https://www.progress.com/network-monitoring. The EPSS score has remained flat at a peak of 0.2175 with no material rise after disclosure.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In WhatsUp Gold versions released before 2024.0.2, an attacker can gain access to the WhatsUp Gold server via the public API.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
T1021.003 Distributed Component Object Model Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-11250Same product class: network monitoring / SIEM
CVE-2022-23131Same product class: network monitoring / SIEM
CVE-2024-36466Same product class: network monitoring / SIEM
CVE-2026-65941Same product: Progress Whatsup Gold
CVE-2024-46909Same product: Progress Whatsup Gold
CVE-2026-65937Same product: Progress Whatsup Gold
CVE-2024-4884Same product: Progress Whatsup Gold
CVE-2024-4883Same product: Progress Whatsup Gold
CVE-2023-6595Same product: Progress Whatsup Gold
CVE-2023-6368Same product: Progress Whatsup Gold

Affected Assets

progress
whatsup gold
23.1.0 — 24.0.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.4.3
  • V10.4.16
  • V11.4.3

Mitigating Controls (NIST 800-53 r5) AI

Proper unique identification and authentication of users directly stops spoofing-based bypass of authentication.

Device identification and authentication before connection prevents spoofing of devices to bypass auth.

Authentication of non-organizational users blocks external spoofing attempts against the scheme.

Authenticator management ensures credentials cannot be easily spoofed or reused to bypass authentication.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-02 partial match
blocks

Proofing and binding identities reduces spoofing opportunities during enrollment but does not address runtime authentication implementation flaws.

PR.AA-03 partial match
blocks

Requiring authentication of users/services/hardware directly counters spoofing-based bypass when strong methods are used.

PR.AA-04 partial match
blocks

Protecting, conveying, and verifying identity assertions specifically prevents the spoofing that enables authentication bypass.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
blocks

A.5.15 only requires that an access control policy and requirements be defined and communicated; it does not itself implement, enforce or configure any authentication scheme that would stop spoofing attacks from bypassing authentication, so the weakness remains fully exploitable.

blocks

A.5.16 manages the lifecycle, uniqueness, and accountability of identities; it does not implement or strengthen authentication schemes against spoofing, so the CWE-290 exploit remains possible even when identities are correctly provisioned and tracked.

blocks

Authentication information management directly addresses credential handling that prevents spoofing.

blocks

A.5.18 governs the provisioning, review, and revocation of already-granted access rights to authenticated identities; it has no bearing on whether an authentication scheme can be spoofed or bypassed before any rights are assigned.

removes

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-290
RHEL 7 (1 rule)
  • V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. blocks CWE-290
RHEL 8 (1 rule)
  • V-230492 RHEL 8 must not have the rsh-server package installed. blocks CWE-290

References