# SUSE-SU-2020:2025-1: Security update for perl-YAML-LibYAML

> An attacker can execute arbitrary code by exploiting unsafe object loading in the Perl YAML library, requiring an update to the package.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2020

## What is SUSE-SU-2020:2025-1?

SUSE-SU-2020:2025-1 is an unsafe deserialization vulnerability in perl-YAML-LibYAML, published on 23 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for perl-YAML-LibYAML fixes the following issues:

perl-YAML-LibYAML was updated to 0.69: [bsc#1173703]

* Security fix: Add $LoadBlessed option to turn on/off loading objects:
  Default is set to true. Note that, the behavior is unchanged.
* Clarify documentation about exported functions
* Dump() was modifying original data, adding a PV to numbers
* Support standard tags !!str, !!map and !!seq instead of dying.
* Support JSON::PP::Boolean and boolean.pm via $YAML::XS::Boolean.
* Fix regex roundtrip. Fix loading of many regexes.

## Which versions are affected by SUSE-SU-2020:2025-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-YAML-LibYAML` | SUSE:Linux Enterprise Module for Development Tools 15 SP1 | All versions | 0.69-3.3.1 |
| `perl-YAML-LibYAML` | SUSE:Linux Enterprise Module for Development Tools 15 SP2 | All versions | 0.69-3.3.1 |

## How do I fix SUSE-SU-2020:2025-1?

Upgrade to a fixed version.

## Is SUSE-SU-2020:2025-1 being exploited?

There is no known exploitation of SUSE-SU-2020:2025-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2020:2025-1 and fix it if it is affected.

What it is: SUSE-SU-2020:2025-1 is an unsafe deserialization vulnerability in perl-YAML-LibYAML, published on 23 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2020:2025-1 in the wild and no public exploit code.

Affected product: perl-YAML-LibYAML. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/SUSE-SU-2020-2025-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2020-2025-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2020:2025-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2020-2025-1/
Summaries are generated and may contain mistakes; the official description above is the record.