LiveActive security incident?Get immediate response
CVE Record

CVE-2018-20618: ok-file-formats through 2018-10-16 has a heap-based buffer over-read in the ok_mo_decode2 function in ok_mo.c.

ok-file-formats through 2018-10-16 has a heap-based buffer over-read in the ok_mo_decode2 function in ok_mo.c.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects ok-file-formats through 2018-10-16. A specially crafted input handled by ok_mo_decode2 can trigger a heap buffer over-read, potentially exposing memory or disrupting applications that parse untrusted files with this code.

Executive priority

Prioritize if the organization uses this library in products or services that parse untrusted files. The impact rating is high, but urgency is lower where there is no embedded use or no attacker-controlled input path.

Technical view

CVE-2018-20618 is a CWE-125 heap-based buffer over-read in ok_mo_decode2 in ok_mo.c. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required.

Likely exposure

Exposure is most likely in applications that embed vulnerable ok-file-formats code and process attacker-controlled or externally supplied inputs through ok_mo_decode2. The provided record does not include CPEs or named downstream products.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates user interaction is required, so risk depends on whether users or services process untrusted files with affected code.

Researcher notes

The public metadata is sparse: affected vendor/product fields are n/a, and the bundle names only the function and upstream issue. Validate exposure by code provenance and parser reachability rather than package inventory alone.

Mitigation direction

  • Inventory any embedded ok-file-formats code or vendored copies.
  • Check the upstream repository and vendor guidance for fixed code or advisories.
  • Avoid processing untrusted inputs with affected ok_mo_decode2 code until remediated.
  • Apply compensating controls around file ingestion and parsing paths.

Validation and detection

  • Search codebases for ok_mo_decode2, ok_mo.c, or vendored ok-file-formats.
  • Confirm whether the embedded snapshot is through 2018-10-16.
  • Identify all public, email, upload, or API paths that parse affected inputs.
  • Review crash reports or sanitizer findings for heap over-read symptoms in this parser.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-125: 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 lookup
cve · low confidence lookup

CVE-2018-20618 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2018-20618Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.