CVE-2018-10917: pulp 2.16.x and possibly older is vulnerable to an improper path parsing

Q: How do I fix CVE-2018-10917?

pulp: upgrade to newer than 2.16.0. Exact commands for each OS are on this page.

Q: Is CVE-2018-10917 being exploited?

CVE-2018-10917 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-10917 affect?

CVE-2018-10917 affects pulp. Severity is medium (CVSS 6.8). pulp 2.16.x and possibly older is vulnerable to an improper path parsing. A malicious user or a malicious iso feed repository can write to locations accessible to the 'apache' user. This may lead to overwrite of published content on other i

Q: How urgent is CVE-2018-10917?

Priority 40/100. No elevated risk signals yet.

This month

MEDIUM 6.8UPGRADE

CVE-2018-10917 is a medium-severity flaw (CVSS 6.8) affecting pulp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

pulp 2.16.x and possibly older is vulnerable to an improper path parsing. A malicious user or a malicious iso feed repository can write to locations accessible to the 'apache' user. This may lead to overwrite of published content on other iso repositories.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.8 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-22
Published	2018-08-15
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: pulpproject

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-08-15 17:29 UTCPublished CVE record published
2026-06-17 01:34 UTCUpdated Record last modified

pulpproject pulp UPGRADE

Affected: <= 2.16.0 · 2.16.1 · 2.16.2 · 2.16.4

Fixed in: newer than 2.16.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pulp || rpm -q pulp || pulp --version

2. UPGRADE to newer than 2.16.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pulp

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pulp

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-10917?

pulp: upgrade to newer than 2.16.0. Exact commands for each OS are on this page.

Is CVE-2018-10917 being exploited?

CVE-2018-10917 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-10917 affect?

CVE-2018-10917 affects pulp. Severity is medium (CVSS 6.8). pulp 2.16.x and possibly older is vulnerable to an improper path parsing. A malicious user or a malicious iso feed repository can write to locations accessible to the 'apache' user. This may lead to overwrite of published content on other i

How urgent is CVE-2018-10917?

Priority 40/100. No elevated risk signals yet.

Related CVEs

CVE-2024-7143 HIGH 8.3 MITIGATE A flaw was found in the Pulp package
CVE-2018-1090 MEDIUM 5.5 UPGRADE MITIGATE In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become
CVE-2016-3704 HIGH 7.5 MITIGATE UPGRADE Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords.
CVE-2016-3696 MEDIUM 5.5 MITIGATE UPGRADE The pulp-qpid-ssl-cfg script in Pulp before 2.8.5 allows local users to obtain the CA key.
CVE-2016-3112 HIGH 7.5 UPGRADE client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cer

References

← Back to latest CVEs