Skip to content
Fencer Intel
medium 5.0

CVE-2015-0206 json

Memory leak in the dtls1_buffer_record function in d1_pkt.c in OpenSSL 1.0.0 before 1.0.0p and 1.0.1 before 1.0.1k allows remote attackers…

published 11y ago modified 4mo ago also EUVD-2015-0243

cvss
5.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
57.4%
EPSS 57.4% chance of exploitation in 30 days, percentile 99%
public exploits
0
none known

Summary

Memory leak in the dtls1_buffer_record function in d1_pkt.c in OpenSSL 1.0.0 before 1.0.0p and 1.0.1 before 1.0.1k allows remote attackers to cause a denial of service (memory consumption) by sending many duplicate records for the next epoch, leading to failure of replay detection.

Patch / fix

  • openssl Debian 14, Debian 13, Debian 12 1.0.1k-1

debian advisories DEBIAN-CVE-2015-0206

  • openssl Ubuntu 14.04 LTS 1.0.1f-1ubuntu2.8

ubuntu advisories UBUNTU-CVE-2015-0206

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • openssl RHEL 6 1.0.1e-30.el6_6.5
  • openssl RHEL 7 1:1.0.1e-34.el7_0.7
  • openssl-libs RHEL 7 1:1.0.1e-34.el7_0.7
  • openssl-perl RHEL 6 1.0.1e-30.el6_6.5
  • openssl-perl RHEL 7 1:1.0.1e-34.el7_0.7

red hat advisories RHSA-2015:0066

  • libressl openSUSE Tumbleweed 2.5.0-1.1
  • openssl-1_1 openSUSE Tumbleweed 1.1.1l-1.2

opensuse advisories openSUSE-SU-2024:10309-1openSUSE-SU-2024:11127-1

Is CVE-2015-0206 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-0206 updated cvss 5.0

openssl: DTLS memory leak in dtls1_buffer_record

  • Red Hat Storage 2 openssl
    affected: no fix available
  • Red Hat Enterprise Linux Client (v. 7) openssl 1.0.1e-34.el7_0.7, openssl-libs 1.0.1e-34.el7_0.7 Red Hat Enterprise Linux Client Optional (v. 7) openssl-perl 1.0.1e-34.el7_0.7 Red Hat Enterprise Linux ComputeNode (v. 7) openssl 1.0.1e-34.el7_0.7, openssl-libs 1.0.1e-34.el7_0.7 Red Hat Enterprise Linux ComputeNode Optional (v. 7) openssl-perl 1.0.1e-34.el7_0.7 Red Hat Enterprise Linux Desktop (v. 6) openssl 1.0.1e-30.el6_6.5 Red Hat Enterprise Linux Desktop Optional (v. 6) openssl-perl 1.0.1e-30.el6_6.5
    +10 more products
    Red Hat Enterprise Linux HPC Node (v. 6) openssl 1.0.1e-30.el6_6.5 Red Hat Enterprise Linux HPC Node Optional (v. 6) openssl-perl 1.0.1e-30.el6_6.5 Red Hat Enterprise Linux Server (v. 6) openssl 1.0.1e-30.el6_6.5 Red Hat Enterprise Linux Server (v. 7) openssl 1.0.1e-34.el7_0.7, openssl-libs 1.0.1e-34.el7_0.7 Red Hat Enterprise Linux Server Optional (v. 6) openssl-perl 1.0.1e-30.el6_6.5 Red Hat Enterprise Linux Server Optional (v. 7) openssl-perl 1.0.1e-34.el7_0.7 Red Hat Enterprise Linux Workstation (v. 6) openssl 1.0.1e-30.el6_6.5 Red Hat Enterprise Linux Workstation (v. 7) openssl 1.0.1e-34.el7_0.7, openssl-libs 1.0.1e-34.el7_0.7 Red Hat Enterprise Linux Workstation Optional (v. 6) openssl-perl 1.0.1e-30.el6_6.5 Red Hat Enterprise Linux Workstation Optional (v. 7) openssl-perl 1.0.1e-34.el7_0.7
    fixed: vendor fix RHSA-2015:0066
  • Red Hat Enterprise Linux 5 openssl, openssl097a Red Hat Enterprise Linux 6 openssl098e Red Hat Enterprise Linux 7 openssl098e Red Hat JBoss Enterprise Application Platform 6 openssl Red Hat JBoss Enterprise Web Server 1 openssl Red Hat JBoss Enterprise Web Server 2 openssl
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

57.36% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.