cve.bz

CVE-2017-20285 Reflection Injection

9.1 criticalEPSS 0.3%

Critical (9.1). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
YAML versions before 1.30 for Perl allow a loaded document to trigger the DESTROY method of arbitrary classes. A perl/hash:Class tag blesses a hash into the class it names. The document supplies the object's fields, and Perl calls DESTROY when it goes out of scope. What DESTROY does depends on the classes the process has loaded. With File::Temp::Dir from core Perl, it can delete a directory tree the document names.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-470 Use of Externally-Controlled Input to Select Classes or Code (Reflection Injection)
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A05:2025 Injection, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-20285 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-20285?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-20285?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-20285 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libyaml-perl1.30-1DEBIAN-CVE-2017-20285
Ubuntu22.04:LTSlibyaml-perl1.30-1ubuntu0.22.04.1USN-8925-1
Ubuntu24.04:LTSlibyaml-perl1.31-1ubuntu0.24.04.1USN-8925-1
UbuntuPro:16.04:LTSlibyaml-perl1.15-1ubuntu0.1~esm1UBUNTU-CVE-2017-20285 USN-8925-1
UbuntuPro:18.04:LTSlibyaml-perl1.24-1ubuntu0.1~esm1UBUNTU-CVE-2017-20285 USN-8925-1
UbuntuPro:20.04:LTSlibyaml-perl1.30-1ubuntu0.20.04.1~esm1USN-8925-1
UbuntuPro:26.04:LTSlibyaml-perl1.31-1ubuntu0.26.04.1~esm1USN-8925-1
Red Hatenterprise_linux:8::appstreamperl-YAML0:1.24-4.module+el8.10.0+25073+d1062575RHSA-2026:93471
openSUSETumbleweedperl-YAML1.321.0-2.1openSUSE-SU-2026:12368-1
AlmaLinux8perl-YAML1.24-4.module_el8.10.0+4341+ab0ec422ALSA-2026:93471
Rocky Linux8perl-YAML0:1.24-4.module+el8.10.0+40403+94558160RLSA-2026:93471
Rocky Linux8perl-YAML0:1.24-4.module+el8.10.0+40403+9457ea6cRLSA-2026:93471
Rocky Linux8perl-YAML0:1.24-4.module+el8.10.0+40403+bd06a93aRLSA-2026:93471
Rocky Linux8perl-YAML0:1.24-4.module+el8.10.0+40403+df14587cRLSA-2026:93471

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because parsing untrusted YAML input enables unprivileged attackers to trigger arbitrary object destructors, potentially resulting in high integrity and availability damage such as unintended filesystem deletion. Within Red Hat Enterprise Linux, the blast radius is determined by whether services or scripts accept unvalidated YAML data from external sources. While exploitation requires compatible Perl modules to be loaded in the process context, it poses a direct risk to applications processing user-supplied documents.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8perl-YAML:1.24-8100020261013125111.ae2fb4b8Fixed 2026-11-02RHSA-2026:93471
Red Hat Enterprise Linux 10perl-YAMLNot affected
Red Hat Enterprise Linux 6perl-YAMLNot affected
Red Hat Enterprise Linux 7perl-YAMLAffected
Red Hat Enterprise Linux 9perl-YAMLNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-20285.

Attack patterns (CAPEC)

  • CAPEC-138 Reflection Injection Severity: Very High
  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON