Cyber 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
View 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 72th percentile
Risk Priority 70 floored blend · peak EPSS

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, ranked in the top 28% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

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)
CWE-489NVD-CWE-Other

Related Threats

CVEs Like This One

CVE-2024-24962Same product: Automationdirect P1-540
CVE-2024-24851Same product: Automationdirect P1-540
CVE-2024-23601Same product: Automationdirect P1-540
CVE-2024-23315Same product: Automationdirect P1-540
CVE-2024-24947Same product: Automationdirect P1-540
CVE-2024-24946Same product: Automationdirect P1-540
CVE-2024-24963Same product: Automationdirect P1-540
CVE-2024-22187Same product: Automationdirect P1-540
CVE-2024-24955Same product: Automationdirect P3-550E
CVE-2024-24958Same product: Automationdirect P3-550E

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

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

SC-25 Thin Nodes
addresses: CWE-489

Minimal functionality precludes inclusion of active debug code or diagnostic interfaces.

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 mostly match
prevents

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.

A.8.29 Security testing in development and acceptance mostly match
detects

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

A.8.9 Configuration management mostly match
prevents

Configuration management can disable or remove debug features through hardened baselines.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates removal of debug code before release.

A.8.28 Secure coding partial match
prevents

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

A.8.31 Separation of development, test and production environments partial match
prevents

Separation of environments reduces risk of debug code reaching production but does not directly address its removal.

A.8.32 Change management partial match
prevents

Change management can enforce removal of debug code as part of release gates.

References