# CVE-2019-25018: Missing authorization in n/a

> Malicious servers can bypass access restrictions to modify target directory permissions on clients using the unsupported rcp client.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Feb 2021
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xxwg-wfjg-vgjp

## What is CVE-2019-25018?

CVE-2019-25018 is a high-severity missing authorization vulnerability in n/a, published on 2 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the rcp client in MIT krb5-appl through 1.0.3, malicious servers could bypass intended access restrictions via the filename of . or an empty filename, similar to CVE-2018-20685 and CVE-2019-7282. The impact is modifying the permissions of the target directory on the client side. NOTE: MIT krb5-appl is not supported upstream but is shipped by a few Linux distributions. The affected code was removed from the supported MIT Kerberos 5 (aka krb5) product many years ago, at version 1.8.

## Which versions are affected by CVE-2019-25018?

It affects 1 product.


Products: Mit Krb5-Appl.

## How do I fix CVE-2019-25018?

Product is end of life, replace it.

## Is CVE-2019-25018 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-25017](https://insights.sbomify.com/CVE-2019-25017/): Path traversal in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25018 and fix it if it is affected.

What it is: CVE-2019-25018 is a high-severity missing authorization vulnerability in n/a, published on 2 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25018 in the wild and no public exploit code.

Affected product: n/a. 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-2019-25018/ (Markdown: https://insights.sbomify.com/CVE-2019-25018/index.md)
```

## Sources

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

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