LiveActive security incident?Get immediate response
CVE Record

CVE-2019-14431: In MatrixSSL 3.8.3 Open through 4.2.1 Open, the DTLS server mishandles incoming network messages leading to...

In MatrixSSL 3.8.3 Open through 4.2.1 Open, the DTLS server mishandles incoming network messages leading to a heap-based buffer overflow of up to 256 bytes and possible Remote Code Execution in parseSSLHandshake in sslDecode.c. During processing of a crafted packet, the server mishandles the fragment length value provided in the DTLS message.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2019-14431 is a critical MatrixSSL DTLS server flaw. A malformed network message can corrupt heap memory and may allow remote code execution. The business risk is highest for products or services exposing MatrixSSL-based DTLS endpoints to untrusted networks.

Executive priority

Treat as high-priority remediation for any exposed DTLS service because the flaw is network-reachable, unauthenticated, and may lead to code execution. Priority drops if MatrixSSL DTLS server functionality is absent or unreachable.

Technical view

MatrixSSL 3.8.3 Open through 4.2.1 Open mishandles the DTLS fragment length during handshake parsing in parseSSLHandshake in sslDecode.c, causing a heap-based buffer overflow of up to 256 bytes and possible remote code execution.

Likely exposure

Exposure is likely limited to systems, appliances, firmware, or applications using affected MatrixSSL Open versions with DTLS server functionality enabled. The source bundle does not provide populated CPEs, so product mapping requires asset and dependency validation.

Exploitation context

The CVSS vector indicates unauthenticated network reachability and low attack complexity. The bundle does not show CISA KEV listing or other evidence of active exploitation, so active exploitation should not be claimed from these sources.

Researcher notes

The provided sources identify the vulnerable function, affected version range, overflow size, and DTLS fragment length handling issue. They do not provide reliable product CPEs, exploit-in-the-wild evidence, or a specific fixed version in the supplied bundle.

Mitigation direction

  • Identify any MatrixSSL Open dependency in the affected version range.
  • Check MatrixSSL vendor guidance and issue tracking for the fixed release or recommended remediation.
  • Prioritize remediation for internet-facing or partner-facing DTLS services.
  • Restrict untrusted network access to affected DTLS endpoints where feasible.
  • Disable unused DTLS server functionality if business operations allow.

Validation and detection

  • Inventory applications, firmware, and third-party components for MatrixSSL usage.
  • Confirm whether DTLS server code paths are enabled and reachable.
  • Compare detected MatrixSSL versions against 3.8.3 Open through 4.2.1 Open.
  • Review perimeter exposure for UDP/DTLS services using MatrixSSL.
  • Track remediation evidence through dependency manifests, vendor attestations, or firmware release notes.
Prepared
Confidence
medium
Sources
3

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-14431 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
Critical
CVSS
9.8 (3.0)
Known Exploited
No
Published

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

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
9.8CVSS 3.0CriticalCVSS:3.0/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

9.8Critical
CVSS 3.0 vector shape for CVE-2019-14431Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

No CWE listed

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