dbcve.org
Debian LinuxOperating system · Debian

CVE-2013-1910

CRITICAL · 9.8 CVSS v3.1 Published 2019-10-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

yum does not properly validate or sanitize repository metadata, allowing a remote attacker controlling a malicious repository to serve specially crafted metadata containing a Trojan horse file. When yum processes this metadata, it can cause denial of service and potentially achieve code execution on the client system.

MitigationOnly use trusted, verified package repositories; ensure GPG signature checking is enabled and functioning for all yum repositories; apply vendor patches for yum to address the metadata handling vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 8.0= 9.0= 10.0
YumApplication
Affected:= 3.4.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed yum version
    Run 'rpm -q yum' or 'yum --version' to determine the installed yum version
    Affected if Version equals 3.4.3 or matches the affected Debian package versions (check via 'dpkg -l | grep yum' on Debian systems)
  2. Verify GPG signature checking is enabled system-wide
    Inspect /etc/yum.conf for 'gpgcheck=1' setting, or check individual repository files in /etc/yum.repos.d/ for 'gpgcheck=1' directives
    Affected if GPG checking is disabled (gpgcheck=0) or the gpgcheck directive is absent from repository configurations
  3. Confirm each configured repository has a GPG key defined
    Review repository .repo files in /etc/yum.repos.d/ and verify each has a 'gpgkey=' directive pointing to a valid key URL
    Affected if Any repository lacks a gpgkey= entry or references an unverified or missing key file
  4. Inspect repository sources for trustworthiness
    List all repository URLs from .repo files in /etc/yum.repos.d/ and from /etc/yum.conf; verify they point to known, trusted vendors or internal mirrors
    Affected if Repositories are configured to point to untrusted, third-party, or unofficial sources

You are affected if your yum version is 3.4.3 or the Debian version is 8.0/9.0/10.0 AND GPG signature verification is disabled or not properly configured for your repositories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Only use trusted, verified package repositories; ensure GPG signature checking is enabled and functioning for all yum repositories; apply vendor patches for yum to address the metadata handling vulnerability.

Recommended fix High confidence

Debian 11 Bullseye or later; yum latest version available in current supported distribution

  1. 1. Back up your current yum configuration and repository settings
  2. 2. For Debian systems: upgrade the entire distribution to a supported release (Debian 11 Bullseye or later) using 'apt-get update && apt-get upgrade' or a fresh installation
  3. 3. For yum specifically: upgrade yum to the latest available version in your distribution's repositories
  4. 4. After upgrade, verify yum functionality with 'yum check-update' or 'yum repolist'
  5. 5. Audit all third-party repository configurations to ensure they are from trusted sources
Caveat Distribution upgrade from Debian 10 to 11 may require testing of existing packages and configurations for compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1910 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1910 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data