# CVE-2018-10917: Path traversal in pulp > A malicious user or ISO feed can exploit improper path parsing to overwrite published content in other repositories. - **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 15 Aug 2018 - **Updated:** 5 Aug 2024 - **Also known as:** RHEA-2019:1283 ## What is CVE-2018-10917? CVE-2018-10917 is a medium-severity path traversal vulnerability in [UNKNOWN] pulp, published on 15 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2018-10917? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kobo` | Red Hat:rhui:3::el7 | All versions | 0:0.5.1-1.el7ui | | `libmodulemd` | Red Hat:rhui:3::el7 | All versions | 0:1.6.3-1.el7ui | | `libmodulemd-debuginfo` | Red Hat:rhui:3::el7 | All versions | 0:1.6.3-1.el7ui | | `libsolv` | Red Hat:rhui:3::el7 | All versions | 0:0.6.34-4.pulp.el7ui | | `libsolv-debuginfo` | Red Hat:rhui:3::el7 | All versions | 0:0.6.34-4.pulp.el7ui | | `libstemmer` | Red Hat:rhui:3::el7 | All versions | 0:0-2.585svn.el7ui | | `libstemmer-debuginfo` | Red Hat:rhui:3::el7 | All versions | 0:0-2.585svn.el7ui | | `mongodb` | Red Hat:rhui:3::el7 | All versions | 0:2.6.11-2.el7ui | | `mongodb-debuginfo` | Red Hat:rhui:3::el7 | All versions | 0:2.6.11-2.el7ui | | `mongodb-server` | Red Hat:rhui:3::el7 | All versions | 0:2.6.11-2.el7ui | | `pulp` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `pulp-admin-client` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `pulp-rpm` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-2.el7ui | | `pulp-rpm-admin-extensions` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-2.el7ui | | `pulp-rpm-plugins` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-2.el7ui | | `pulp-selinux` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `pulp-server` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `python-amqp` | Red Hat:rhui:3::el7 | All versions | 0:2.2.2-3.el7ui | | `python-billiard` | Red Hat:rhui:3::el7 | All versions | 1:3.5.0.3-3.el7ui | | `python-billiard-debuginfo` | Red Hat:rhui:3::el7 | All versions | 1:3.5.0.3-3.el7ui | | `python-celery` | Red Hat:rhui:3::el7 | All versions | 0:4.0.2-5.el7ui | | `python-django` | Red Hat:rhui:3::el7 | All versions | 0:1.11.13-1.el7ui | | `python-kid` | Red Hat:rhui:3::el7 | All versions | 0:0.9.6-11.el7ui | | `python-kombu` | Red Hat:rhui:3::el7 | All versions | 1:4.0.2-9.el7ui | | `python-pulp-bindings` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `python-pulp-client-lib` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `python-pulp-common` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `python-pulp-oid_validation` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `python-pulp-repoauth` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-3.el7ui | | `python-pulp-rpm-common` | Red Hat:rhui:3::el7 | All versions | 0:2.18.1.1-2.el7ui | | `python-vine` | Red Hat:rhui:3::el7 | All versions | 0:1.1.3-4.el7ui | | `python2-amqp` | Red Hat:rhui:3::el7 | All versions | 0:2.2.2-3.el7ui | | `python2-billiard` | Red Hat:rhui:3::el7 | All versions | 1:3.5.0.3-3.el7ui | | `python2-celery` | Red Hat:rhui:3::el7 | All versions | 0:4.0.2-5.el7ui | | `python2-django` | Red Hat:rhui:3::el7 | All versions | 0:1.11.13-1.el7ui | | `python2-kombu` | Red Hat:rhui:3::el7 | All versions | 1:4.0.2-9.el7ui | | `python2-solv` | Red Hat:rhui:3::el7 | All versions | 0:0.6.34-4.pulp.el7ui | | `python2-vine` | Red Hat:rhui:3::el7 | All versions | 0:1.1.3-4.el7ui | | `repoview` | Red Hat:rhui:3::el7 | All versions | 0:0.6.6-4.el7ui | | `rh-rhui-tools` | Red Hat:rhui:3::el7 | All versions | 0:3.1.1-2 | Products: Pulpproject Pulp. ## How do I fix CVE-2018-10917? Apply the vendor's patch. ## Is CVE-2018-10917 being exploited? There is no known exploitation of CVE-2018-10917 in the wild and no public exploit code. ## Other vulnerabilities in [UNKNOWN] pulp - [CVE-2015-5263](https://insights.sbomify.com/CVE-2015-5263/): Security feature bypass in n/a (high 8.1) - [CVE-2016-3112](https://insights.sbomify.com/CVE-2016-3112/): Information disclosure in n/a (high 7.5) - [CVE-2013-7450](https://insights.sbomify.com/CVE-2013-7450/): Hardcoded credentials in n/a (high 7.5) - [CVE-2016-3108](https://insights.sbomify.com/CVE-2016-3108/): Path traversal in n/a (high 7.1) - [CVE-2024-7143](https://insights.sbomify.com/CVE-2024-7143/): Pulpcore: rbac permissions incorrectly assigned in tasks that create objects (medium 6.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-10917 and fix it if it is affected. What it is: CVE-2018-10917 is a medium-severity path traversal vulnerability in [UNKNOWN] pulp, published on 15 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2018-10917 in the wild and no public exploit code. Affected product: [UNKNOWN] pulp. 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/CVE-2018-10917/ (Markdown: https://insights.sbomify.com/CVE-2018-10917/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10917 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10917 - OSV: https://osv.dev/vulnerability/CVE-2018-10917 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-10917/ Summaries are generated and may contain mistakes; the official description above is the record.