Security Resilience

CVE-2024-13871

Command Injection in Bitdefender Box Firmware 1.3.11.490

Published
12 March 2025
Modified
30 July 2025
Patch / advisory
CVSS Score v4 9.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0077 55th percentile
Risk Priority 45 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-13871 is a critical-severity Command Injection (CWE-77) vulnerability in Bitdefender Box Firmware. Its CVSS base score is 9.4 (Critical).

Operationally, ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — 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-13871 is a command injection vulnerability (CWE-77) in the /check_image_and_trigger_recovery API endpoint of Bitdefender Box 1 running firmware version 1.3.11.490. Published on 2025-03-12, it carries a CVSS v3.1 base score of 8.8 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to its potential for significant impact on the affected device.

An unauthenticated, network-adjacent attacker can exploit this vulnerability with low complexity and no required privileges or user interaction. Successful exploitation allows execution of arbitrary commands on the device, potentially resulting in full remote code execution (RCE) and compromise of confidentiality, integrity, and availability.

Bitdefender has issued a security advisory on the unauthenticated command injection in Bitdefender Box V1, available at https://bitdefender.com/support/security-advisories/unauthenticated-command-injection-in-bitdefender-box-v1, which security practitioners should review for details on mitigation and patching.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A command injection vulnerability exists in the /check_image_and_trigger_recovery API endpoint of Bitdefender Box 1 (firmware version 1.3.11.490). This flaw allows an unauthenticated, network-adjacent attacker to execute arbitrary commands on the device, potentially leading to full remote code execution (RCE).

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-13872Same product: Bitdefender Box
CVE-2024-13870Same product: Bitdefender Box
CVE-2026-10046Same vendor: Bitdefender
CVE-2023-6056Same vendor: Bitdefender
CVE-2025-2243Same vendor: Bitdefender
CVE-2023-49567Same vendor: Bitdefender
CVE-2023-6058Same vendor: Bitdefender
CVE-2024-2224Same vendor: Bitdefender
CVE-2025-2245Same vendor: Bitdefender
CVE-2023-6154Same vendor: Bitdefender

Affected Assets

bitdefender
box firmware
1.3.11.490

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Secure engineering principles include proper neutralization and safe command construction practices.

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 guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

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-77, a class-level weakness, and none of its children carries one either.

References