Secuno
ENNL
Book demo

CVE-2024-36702

Mz-automation Libiec61850 buffer overflow

7.4 HIGHPublic exploitEPSS 0.25%
  1. Published11 Jun 2024

Description

libiec61850 v1.5 was discovered to contain a heap overflow via the BerEncoder_encodeLength function at /asn1/ber_encoder.c.

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Mz-automation Libiec618501.5

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-1078158.5
MariaDB server is a community developed fork of MySQL server. From 10.6.1 until…
CVE-2026-195708.8
The LE Audio Broadcast Sink in subsys/bluetooth/audio/bap_broadcast_sink.c copies…
CVE-2026-1079099.1
A heap-based out-of-bounds write in the ws_read_frame function (src/bolt/ws.c) and the…
CVE-2026-1079089.8
A heap-based out-of-bounds write in the BoltReadHandler function (src/bolt/bolt_api.c)…
CVE-2026-823448.1
IBM Guardium Data Protection 12.0, 12.1 is vulnerable to a heap-based buffer overflow…
CVE-2026-823358.1
IBM Guardium Data Protection 12.0, 12.1, 12.2 is vulnerable to a heap-based buffer…

Frequently asked

Is CVE-2024-36702 being actively exploited?

CVE-2024-36702 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.25%.

How severe is CVE-2024-36702?

CVE-2024-36702 has a CVSS 3.1 base score of 7.4, rated high. EPSS estimates a 0.25% probability of exploitation.

Which products are affected by CVE-2024-36702?

Affected products include Mz-automation Libiec61850.

How do I fix CVE-2024-36702?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-36702 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.