CVE-2024-13872: Bitdefender Box Insecure Update Mechanism Vulnerability in libboxhermes.so

Published Mar 12, 2025
·
Updated

Bitdefender Box, versions 1.3.11.490 through 1.3.11.505, uses the insecure HTTP protocol to download assets over the Internet to update and restart daemons and detection rules on the devices. Updates can be remotely triggered through the /settemptoken API method. Then, an unauthenticated and network-adjacent attacker can use man-in-the-middle (MITM) techniques to return malicious responses. Restarted daemons that use malicious assets can then be exploited for remote code execution on the device.

Affected Software

3 affected components
Bitdefender BOX>=1.3.11.490<=1.3.11.505
All of the following
Bitdefender BOX firmware>=1.3.11.490<=1.3.11.505
Bitdefender BOX

Remediation

Information

An automatic update to version 1.3.11.505 fixes the issue.

Event History

Mar 12, 2025
CVE Published
via MITRE·11:47 AM
Data Sourced
via MITRE·11:47 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·12:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-13872?

CVE-2024-13872 is considered a high severity vulnerability due to the use of insecure HTTP protocol for downloading updates.

2

How do I fix CVE-2024-13872?

To fix CVE-2024-13872, update your Bitdefender Box to version 1.3.11.506 or later, which resolves the insecure update mechanism.

3

What versions of Bitdefender Box are affected by CVE-2024-13872?

CVE-2024-13872 affects Bitdefender Box versions from 1.3.11.490 to 1.3.11.505.

4

What can an attacker do by exploiting CVE-2024-13872?

An attacker exploiting CVE-2024-13872 could potentially download malicious assets to the device due to the insecure update mechanism.

5

Is there a workaround for CVE-2024-13872 until a fix is applied?

There is no official workaround for CVE-2024-13872 other than upgrading to the fixed version as soon as possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203