LiveActive security incident?Get immediate response
CVE Record

CVE-2017-18187: In ARM mbed TLS before 2.7.0, there is a bounds-check bypass through an integer overflow in PSK identity pa...

In ARM mbed TLS before 2.7.0, there is a bounds-check bypass through an integer overflow in PSK identity parsing in the ssl_parse_client_psk_identity() function in library/ssl_srv.c.

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

Security readout for executives and security teams

Plain-English summary

This vulnerability affects ARM mbed TLS before 2.7.0. A flaw in how server-side PSK identity data is parsed can bypass a bounds check through integer overflow. Business urgency depends on whether products or services embed affected mbed TLS versions and use PSK-based TLS server functionality.

Executive priority

Treat this as an exposure-discovery item unless affected mbed TLS is confirmed in externally reachable services or embedded products. There is no active exploitation evidence in the supplied sources, but old TLS libraries can persist in appliances and statically linked software.

Technical view

CVE-2017-18187 is an integer overflow in ssl_parse_client_psk_identity() in library/ssl_srv.c before mbed TLS 2.7.0. The issue is described as a bounds-check bypass during PSK identity parsing. The supplied sources do not provide CVSS, CWE, confirmed impact details, or active exploitation evidence.

Likely exposure

Exposure is most likely in applications, appliances, firmware, or distribution packages that include ARM mbed TLS before 2.7.0. Priority is higher where the software accepts TLS client connections using PSK identity parsing. Distribution advisories from Debian, Gentoo, and Ubuntu indicate downstream package relevance.

Exploitation context

The source bundle marks KEV as false and contains no cited evidence of active exploitation. The vulnerability is in TLS server parsing logic, so reachability depends on affected mbed TLS being present and the relevant PSK server code path being exposed.

Researcher notes

Key unknowns are impact severity, exploitability, and affected downstream version mapping. Start by confirming the exact mbed TLS version or backport status, then determine whether the PSK server parsing path is reachable. Avoid assuming non-PSK TLS deployments are affected without code-path evidence.

Mitigation direction

  • Upgrade ARM mbed TLS to 2.7.0 or a later supported release.
  • Apply fixed vendor or distribution packages from Debian, Gentoo, Ubuntu, or your platform vendor.
  • Check embedded and statically linked products for bundled mbed TLS copies.
  • Review vendor guidance before using configuration workarounds as compensating controls.

Validation and detection

  • Inventory packages, SBOMs, firmware, and source trees for mbed TLS before 2.7.0.
  • Check for vendored mbed TLS code, especially library/ssl_srv.c.
  • Confirm whether TLS server PSK identity parsing is enabled or reachable.
  • Verify patched builds include the upstream ARM mbed TLS fix or distro backport.
Prepared
Confidence
medium
Sources
8

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-2017-18187 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
7Source 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.