dbcve.org
ModulemdPlugin / extension · Redhat

CVE-2017-1002157

CRITICAL · 9.8 CVSS v3.1 Published 2019-01-10
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
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
modulemd 1.3.1 and earlier uses an unsafe function for processing externally provided data, leading to remote code execution.

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

modulemd versions 1.3.1 and earlier contain a vulnerability where an unsafe function processes externally provided data, allowing remote code execution. The specific vulnerable function and attack vector are not detailed in available references, but the critical CVSS score indicates trivial exploitability leading to RCE.

MitigationUpgrade modulemd to version 1.3.2 or later which contains the security fix. If upgrade is not immediately possible, restrict network access to systems using this library and sanitize any external inputs before processing.

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
ModulemdPlugin / extension
Affected:<= 1.3.1

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. Detect if modulemd library is installed
    Search for the modulemd library on the system using package managers or file searches. On RHEL/CentOS: rpm -qa | grep modulemd. On Fedora: dnf list installed | grep modulemd. Also check for library files: find /usr/lib* -name '*modulemd*' 2>/dev/null
    Affected if The modulemd package or library file is found on the system
  2. Retrieve the installed modulemd version
    Run the appropriate package query command: rpm -q modulemd (RHEL/CentOS), dnf list installed modulemd (Fedora), or check the library file version with: rpm -qi modulemd or dpkg -l | grep modulemd (Debian-based)
    Affected if The version displayed is 1.3.1 or any version lower than 1.3.1
  3. Identify applications or services using modulemd
    Search for binaries or services that link to the modulemd library: ldd $(which <service>) 2>/dev/null | grep modulemd, or check application dependencies. Also review any custom applications that import or use the modulemd Python module: python3 -c 'import modulemd; print(modulemd.__version__)' 2>/dev/null
    Affected if Any application or service on the system links to or imports the vulnerable modulemd library version 1.3.1 or earlier
  4. Review external data inputs to modulemd processing
    Audit logs, application traffic, or input sources that feed data to modulemd processing functions. Check if the system processes external module metadata streams, YAML files from untrusted sources, or network-received module definitions
    Affected if The system processes untrusted or externally-sourced data through modulemd, particularly module metadata streams from network sources or untrusted repositories

The system is affected if modulemd version 1.3.1 or earlier is installed AND any application uses it to process external data inputs, as the unsafe function in this version allows remote code execution.

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
Upgrade available Upgrade to a release after 1.3.1
Interim mitigation

Upgrade modulemd to version 1.3.2 or later which contains the security fix. If upgrade is not immediately possible, restrict network access to systems using this library and sanitize any external inputs before processing.

Recommended fix Moderate confidence

Any version of modulemd > 1.3.1 (e.g., 1.4.0 or later stable release)

  1. 1. Identify the current version of modulemd installed: rpm -qa | grep modulemd or pip show modulemd
  2. 2. Upgrade modulemd to a version newer than 1.3.1. For RPM-based systems: sudo yum update modulemd or sudo dnf update modulemd
  3. 3. For Python pip installations: pip install --upgrade modulemd
  4. 4. Verify the new version is installed: rpm -qa | grep modulemd or pip show modulemd
  5. 5. Test that dependent applications still function correctly after the upgrade
Caveat Minor version upgrades within the same major series typically have backward compatibility, but test in a non-production environment first

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

Fix this in Modulemd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1002157 — 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-2017-1002157 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