DHI-mkpj-fjqt-t4vy-4syf

Source
https://scout.docker.com/v/DHI-mkpj-fjqt-t4vy-4syf
Import Source
https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-mkpj-fjqt-t4vy-4syf.json
JSON Data
https://api.osv.dev/v1/vulns/DHI-mkpj-fjqt-t4vy-4syf
Upstream
Published
2026-11-19T00:29:06Z
Modified
2026-11-21T20:45:03Z
Severity
  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CVSS Calculator
Summary
Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may
Details

Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.

Impact summary: A remote attacker can send a few small crafted DTLS handshake fragments to make a DTLS server or client allocate well over a megabyte of memory per connection, which may lead to memory exhaustion and Denial of Service if many connections are made.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: DTLS handshake messages can arrive out of order and fragmented, so OpenSSL buffers fragments of up to ten out-of-sequence messages until reassembly is possible. When the first fragment of a new message arrives, OpenSSL allocates a buffer sized to the full message length declared in the fragment header, plus a reassembly bitmap, instead of storing only the bytes actually received. The declared length is capped by the maximum certificate list size, 128KB by default, and that cap applies to every handshake message type rather than only to Certificate messages.

Only DTLS endpoints reach this code. TLS, QUIC and applications that do not use DTLS are unaffected. An attacker sends fragments that declare a large message length but carry almost no data, using up to ten distinct message sequence numbers.

A single connection can then hold roughly 1.4MB of buffers from about 156 bytes on the wire. Because the number of buffered messages is capped, memory exhaustion requires many connections or many peers, which is why the severity is Low.

FIPS impact: no The affected code is outside the FIPS module boundary.

Database specific
{
    "coverage": "partial",
    "coverage_exclusions": [
        "legacy_package_image_owner"
    ]
}
References

Affected packages

Docker Hardened Images:Debian:13 / openssl

Package

Name
openssl
Purl
pkg:deb/dhi/openssl

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0 Unknown introduced version / All previous versions are affected

Affected versions

3.*
3.5.5-1~deb13u2dhi0
3.5.6-1~deb13u1dhi0
3.5.6-1~deb13u1+dhi0
3.5.6-1~deb13u1+dhi1
3.5.6-1~deb13u1+dhi2
3.5.6-1~deb13u1+fips+dhi0
3.5.6-1~deb13u1+fips+dhi1
3.5.6-1~deb13u1+fips+dhi2
3.5.6-1~deb13u2+dhi0
3.5.6-1~deb13u2+dhi1
3.5.6-1~deb13u2+dhi2
3.5.6-1~deb13u2+dhi3
3.5.6-1~deb13u2+fips+dhi0
3.5.6-1~deb13u2+fips+dhi1
3.5.7-1~deb13u2+dhi0
3.5.7-1~deb13u2+dhi1
3.5.7-1~deb13u2+fips+dhi0
3.5.7-1~deb13u3+dhi0
3.5.7-1~deb13u3+dhi1
3.5.7-1~deb13u3+dhi2
3.5.7-1~deb13u3+dhi3
3.5.7-1~deb13u3+fips+dhi0
3.5.9-1~deb13u1+dhi0
3.5.9-1~deb13u1+fips+dhi0

Database specific

owner_kind
"HSP"
source
"https://github.com/docker-hardened-images/advisories/blob/main/dhi/osv/2026/DHI-mkpj-fjqt-t4vy-4syf.json"