# openSUSE-SU-2019:2612-1: Security update for libxml2

> This update corrects the changelog for libxml2 to accurately reflect previously fixed CVEs, without addressing new security issues.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 3 Dec 2019

## What is openSUSE-SU-2019:2612-1?

openSUSE-SU-2019:2612-1 is a vulnerability in libxml2, published on 3 Dec 2019. 

### Official description

This update for libxml2 doesn't fix any additional security issues, but correct its rpm changelog to reflect
all CVEs that have been fixed over the past.
This update was imported from the SUSE:SLE-15:Update update project.

## Which versions are affected by openSUSE-SU-2019:2612-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libxml2` | openSUSE:Leap 15.1 | All versions | 2.9.7-lp151.5.6.1 |
| `python-libxml2-python` | openSUSE:Leap 15.1 | All versions | 2.9.7-lp151.5.6.1 |

## How do I fix openSUSE-SU-2019:2612-1?

Apply the vendor's patch.

## Is openSUSE-SU-2019:2612-1 being exploited?

There is no known exploitation of openSUSE-SU-2019:2612-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for openSUSE-SU-2019:2612-1 and fix it if it is affected.

What it is: openSUSE-SU-2019:2612-1 is a vulnerability in libxml2, published on 3 Dec 2019. 
Exploitation: There is no known exploitation of openSUSE-SU-2019:2612-1 in the wild and no public exploit code.

Affected product: libxml2. 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/openSUSE-SU-2019-2612-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2019-2612-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2019:2612-1

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