Skip to content
Web

CVE-2024-14033

8.7
High
EPSS 0.43%Apr 3, 2026

Heap overflow in HiLCOS web interface enables unauthenticated DoS via crafted requests.

common questions

Is CVE-2024-14033 being exploited?

Not confirmed. CVE-2024-14033 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.

How severe is CVE-2024-14033?

CVE-2024-14033 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-14033?

Not known from our data. No patch reference has been recorded for CVE-2024-14033, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2024-14033 affect?

CVE-2024-14033 affects Hirschmann BAT-R, Hirschmann BAT-F, Hirschmann BAT450-F, Hirschmann BAT867-R, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2024-14033?

Patch when available; restrict web access to trusted networks.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Hirschmann BAT-RHirschmann BAT-FHirschmann BAT450-FHirschmann BAT867-RHirschmann BAT867-FHirschmann WLCBAT Controller Virtual
impact

Unauthenticated remote DoS: heap overflow crashes devices and disrupts OT services (Public Spot config).

action required

Patch when possible

affected versions
Belden Hirschmann EagleSDV
  • affected< 05.4.01
vendor says fixed in05.4.02

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free