LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9989: ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 has a buffer over-read in ssl_parse_server_psk_h...

ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 has a buffer over-read in ssl_parse_server_psk_hint() that could cause a crash on invalid input.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9989 is a crash-risk flaw in older ARM mbed TLS releases. Invalid input during TLS pre-shared-key hint handling can trigger a buffer over-read. The main business concern is service availability for products or services that embed vulnerable mbed TLS versions.

Executive priority

Treat this as a targeted availability remediation item. It is not supported as actively exploited in the provided evidence, but vulnerable TLS libraries can be hidden in products, so inventory and patch verification matter.

Technical view

ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 contains a buffer over-read in ssl_parse_server_psk_hint(). Public sources describe a possible crash on invalid input, but the bundle does not provide CVSS, CWE, detailed affected CPEs, or exploit evidence.

Likely exposure

Exposure is most likely in applications, appliances, embedded systems, or Linux packages that bundle ARM mbed TLS or older PolarSSL-derived packages below the fixed release lines. The source bundle does not identify specific downstream products.

Exploitation context

No active exploitation is supported by the provided sources, and the CVE is not listed as KEV in the bundle. The documented impact is a crash from invalid input, suggesting availability risk rather than confirmed code execution.

Researcher notes

The key technical artifact is ssl_parse_server_psk_hint() and the referenced upstream commits. Evidence is incomplete for exploitability beyond crash behavior, affected downstream products, and scoring; do not infer broader impact without vendor confirmation.

Mitigation direction

  • Upgrade mbed TLS to 2.1.11, 2.7.2, 2.8.0, or a later fixed release.
  • Apply relevant distribution security updates, including Debian LTS polarssl or mbedtls packages where applicable.
  • Inventory bundled mbed TLS copies inside firmware, containers, appliances, and statically linked applications.
  • For third-party products, check vendor firmware or support advisories for incorporated mbed TLS fixes.

Validation and detection

  • Confirm deployed mbed TLS or PolarSSL package versions against the fixed release thresholds.
  • Review dependency manifests, SBOMs, and static-link build records for embedded mbed TLS copies.
  • Check Debian package changelogs or advisory references where Debian LTS packages are used.
  • Prioritize validation on internet-facing or untrusted-network TLS services using PSK configurations.
Prepared
Confidence
medium
Sources
7

Public sources used

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.

cve · low confidence lookup

CVE-2018-9989 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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