Security Resilience

CVE-2024-21785

Automationdirect P3-550E Firmware 1.2.10.9 … 4.1.1.10

Public PoC
Published
28 May 2024
Modified
12 February 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.015 74th percentile
Risk Priority 74 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-21785 is a critical-severity Active Debug Code (CWE-489) vulnerability in Automationdirect P3-550E Firmware. Its CVSS base score is 9.8 (Critical).

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

The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A leftover debug code vulnerability exists in the Telnet Diagnostic Interface functionality of AutomationDirect P3-550E 1.2.10.9. A specially crafted series of network requests can lead to unauthorized access. An attacker can send a sequence of requests to trigger this vulnerability.

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.
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1008 Fallback Channels Command And Control
Adversaries may use fallback or alternate communication channels if the primary channel is compromised or inaccessible in order to maintain reliable command and control and to avoid data transfer thresholds.
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
T1016.001 Internet Connection Discovery Discovery
Adversaries may check for Internet connectivity on compromised systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-24962Same product: Automationdirect P1-540
CVE-2024-24963Same product: Automationdirect P1-540
CVE-2024-24851Same product: Automationdirect P1-540
CVE-2024-23601Same product: Automationdirect P1-540
CVE-2024-24946Same product: Automationdirect P1-540
CVE-2024-24947Same product: Automationdirect P1-540
CVE-2024-22187Same product: Automationdirect P1-540
CVE-2024-23315Same product: Automationdirect P1-540
CVE-2024-53648Shared CWE-489
CVE-2024-28008Shared CWE-489

Affected Assets

automationdirect
p3-550e firmware
1.2.10.9, 4.1.1.10
automationdirect
p3-550 firmware
1.2.10.9, 4.1.1.10
automationdirect
p3-530 firmware
1.2.10.9, 4.1.1.10
automationdirect
p2-550 firmware
1.2.10.10, 4.1.1.10
automationdirect
p1-550 firmware
1.2.10.10, 4.1.1.10
automationdirect
p1-540 firmware
1.2.10.10, 4.1.1.10

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Baseline configuration defines the approved production state that must exclude active debug code.

Least functionality explicitly prohibits enabling unnecessary debug or diagnostic features in production builds.

Documented development standards and tools can require removal of debug code before release.

Security-integrated SDLC processes ensure debug artifacts are stripped prior to deployment.

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.PS-06 partial match
blocks

Secure SDLC practices directly require removal of debug code before release, covering most of this weakness while the control addresses many other development issues.

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

A.8.25 mandates secure SDLC practices including secure coding, security testing, checkpoints, and developer training that reduce the chance of shipping active debug code, but does not guarantee its absence in every release (e.g. via incomplete enforcement or outsourced gaps).

prevents

Secure coding standards explicitly prohibit leaving debug code active in production.

finds

Security testing in development and acceptance catches active debug code before deployment.

blocks

A.8.31 separates environments and controls movement between them but does not stop active debug code from remaining present and exploitable in a released production build

References