Skip to content
Networks

CVE-2015-10148

8.8
High
EPSS 0.29%Patch availableApr 4, 2026

Default keys in HiLCOS devices enable MITM on management traffic.

common questions

Is CVE-2015-10148 being exploited?

Not confirmed. CVE-2015-10148 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.29% probability of exploitation in the next 30 days.

How severe is CVE-2015-10148?

CVE-2015-10148 is rated High with a CVSS score of 8.8. 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-2015-10148?

Yes. A fix has been recorded for CVE-2015-10148. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2015-10148 affect?

CVE-2015-10148 affects Hirschmann HiLCOS OpenBAT, Hirschmann HiLCOS WLC, Hirschmann HiLCOS BAT300, Hirschmann HiLCOS BAT54, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2015-10148?

Upgrade to patched firmware; secure management channels.

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

executive summary
technical analysis
affected
Hirschmann HiLCOS OpenBATHirschmann HiLCOS WLCHirschmann HiLCOS BAT300Hirschmann HiLCOS BAT54OpenBAT firmware < 9.10 / 8.80
impact

Unauthenticated attackers can decrypt/intercept management traffic, impersonate devices, and expose sensitive data via shared default keys.

action required

Patch when possible

affected versions
Belden Hirschmann HiLCOS
  • affected>= 9.00 and <= 9.00-RU1
  • affected<= 8.80
vendor says fixed in9.10

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