Security readout for executives and security teams
Plain-English summary
CVE-2024-36702 is a heap overflow reported in libiec61850 v1.5. If an exposed application includes this vulnerable library, successful exploitation could affect confidentiality, integrity, and availability. The public record does not identify downstream products or a named patch.
Executive priority
Treat this as a high-priority exposure discovery item, especially for operational or embedded systems. The main business task is determining whether the library exists in your environment before assigning remediation deadlines.
Technical view
The flaw is CWE-122 in BerEncoder_encodeLength at /asn1/ber_encoder.c. CVSS 3.1 is 7.4: local attack vector, high complexity, no privileges, no user interaction, unchanged scope, and high C/I/A impact.
Likely exposure
Exposure is most likely where libiec61850 v1.5 is directly used, statically linked, or embedded. The CVE data lists no CPEs, vendor/product mappings, or downstream affected products, so asset confirmation is required.
Exploitation context
The source bundle says this CVE is not in KEV. No cited source states active exploitation. The CVSS vector indicates local access and high attack complexity, but potentially severe impact if the vulnerable path is reachable.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, CWE, upstream repository, and GitHub issue reference. No exploit status, fixed version, commit, or affected downstream product list is provided in the bundle.
Mitigation direction
- Inventory applications, firmware, and builds for libiec61850 v1.5.
- Check the upstream repository and issue 505 for vendor guidance.
- Ask downstream vendors whether their products embed the affected library version.
- Apply an upstream or vendor-supported update when one is identified.
- Limit local access to systems confirmed to include the vulnerable library.
Validation and detection
- Review SBOMs and build manifests for libiec61850 v1.5.
- Search vendored source for /asn1/ber_encoder.c and BerEncoder_encodeLength.
- Confirm whether local users or processes can reach the affected code path.
- Track the CVE record for affected product or fix updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-36702 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H1.45.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/mz-automation/libiec61850CVE reference, mitre
- https://github.com/mz-automation/libiec61850/issues/505CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.