# CVE-2017-9270: post-auth arbitrary file write on cryptctl server

> A malicious server can send RPC requests to overwrite files outside the key database, allowing arbitrary file modification.

- **Severity:** High 8.7 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-whc2-8cpp-f5cp, SUSE-SU-2017:1865-1

## What is CVE-2017-9270?

CVE-2017-9270 is a high-severity path traversal vulnerability in SUSE cryptctl, published on 1 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In cryptctl before version 2.0 a malicious server could send RPC requests that could overwrite files outside of the cryptctl key database.

Weakness: CWE-20 (Improper Input Validation), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2017-9270?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cryptctl` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.2.6-5.3.11 |

Products: Opensuse Cryptctl.

## How do I fix CVE-2017-9270?

Upgrade to a fixed version.

## Is CVE-2017-9270 being exploited?

There is no known exploitation of CVE-2017-9270 in the wild and no public exploit code.

## Other vulnerabilities in SUSE cryptctl

- [CVE-2019-18906](https://insights.sbomify.com/CVE-2019-18906/): cryptctl: client side password hashing is equivalent to clear text password storage (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9270 and fix it if it is affected.

What it is: CVE-2017-9270 is a high-severity path traversal vulnerability in SUSE cryptctl, published on 1 Mar 2018. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9270 in the wild and no public exploit code.

Affected product: SUSE cryptctl. 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-2017-9270/ (Markdown: https://insights.sbomify.com/CVE-2017-9270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9270
- OSV: https://osv.dev/vulnerability/CVE-2017-9270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9270/
Summaries are generated and may contain mistakes; the official description above is the record.