Security Resilience

CVE-2024-11322

Auth Bypass

Published
15 January 2025
Modified
15 April 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0062 49th percentile
Risk Priority 59 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-11322 is a high-severity Improper Authentication (CWE-287) vulnerability. Its CVSS base score is 7.5 (High).

Operationally, ranked at the 49th percentile by exploit likelihood (below the median); 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.

CVE-2024-11322 is a denial-of-service vulnerability in CyberPower PowerPanel Business (PPB) version 4.11.0. The issue stems from the PowerPanel Business Service Watchdog service, which listens on TCP port 2003 and allows an unauthenticated remote attacker to restart the ppbd.exe process. Repeated restarts of this process can render it unavailable, leading to service disruption. The vulnerability is rated with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and is associated with CWE-287 (Improper Authentication).

An unauthenticated attacker with network access to the affected system can exploit this vulnerability by sending requests to TCP port 2003, triggering the watchdog service to restart ppbd.exe. By repeating the attack, the attacker can repeatedly crash and restart the process, causing a denial-of-service condition that impacts the availability of PowerPanel Business functions. No privileges, user interaction, or scope changes are required, making it straightforward to exploit remotely.

The Tenable advisory at https://www.tenable.com/security/research/tra-2025-01 provides further details on the vulnerability, including potential mitigation steps. Published on 2025-01-15, no patches or specific workarounds are detailed in the provided information.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A denial-of-service vulnerability exists in CyberPower PowerPanel Business (PPB) 4.11.0. An unauthenticated remote attacker can restart the ppbd.exe process via the PowerPanel Business Service Watchdog service listening on TCP port 2003. The attacker can repeatedly restart ppbd.exe to render it…

more

unavailable.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-49197Shared CWE-287
CVE-2021-41303Shared CWE-287
CVE-2026-56345Shared CWE-287
CVE-2023-3597Shared CWE-287
CVE-2024-37408Shared CWE-287
CVE-2024-28012Shared CWE-287
CVE-2026-61435Shared CWE-287
CVE-2026-75800Shared CWE-287
CVE-2026-15542Shared CWE-287
CVE-2023-35078Shared CWE-287

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Mandates unique identification and authentication of organizational users before access, directly stopping improper authentication.

Requires unique identification and authentication of devices before establishing connections, preventing unauthenticated device claims.

Mandates unique identification and authentication of non-organizational users, directly addressing the weakness for external actors.

Manages authenticators with verification and secure distribution, reducing opportunities for improper authentication.

Enforces access only after approved authorizations, which presupposes correct authentication has occurred.

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.

blocks

Mandating segregated approval and oversight for non-human identities reduces the chance that weak or orphaned credentials can be exploited for unauthorized authentication.

blocks

A.5.17 directly mandates generation of non-guessable unique secrets, secure transmission, immediate change of defaults/temporary creds, strong password enforcement, no-reuse, and compromise response, which stops most improper-authentication exploits at source; the bounded remainder is non-password authentication methods and sufficiency-of-proof cases (e.g. IA-2/IA-5 enhancements) left to other controls.

blocks

Security requirements specified early and verified through testing drive the consistent implementation of authentication mechanisms, decreasing the likelihood that authentication steps are omitted or incorrectly applied.

blocks

A.8.26 explicitly requires identifying and addressing authentication-related requirements (including level of trust in identity via 8.5 and 5.17) as part of application development or acquisition, which prevents a slice of CWE-287 but leaves the dominant sufficiency-of-proof aspects (IA-2/IA-5) and many implementation defects untouched.

blocks

A.8.27 mandates security-by-design principles (least privilege, default-deny, never-trust/always-verify, MFA, end-to-end encryption of requests, distrust-external-input, secure session control, and explicit authentication/authorization in every layer), which directly stops most improper-authentication flaws from being exploitable; the bounded remainder is insufficient-proof cases that live only in the strength or correctness of the credential itself (IA-5/IA-2 territory).

blocks

A.8.5 directly mandates appropriate-strength authentication techniques, MFA for critical systems, protected log-on procedures, brute-force resistance, no cleartext passwords/transmission, and session controls that stop exploitation of insufficient proof of identity; the bounded remainder is cases where the chosen technique itself is flawed or insufficiently implemented (e.g. weak biometrics without fallback).

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-287, a class-level weakness. Rules are authored against its narrower children: CWE-295, CWE-306.

References