# CVE-2013-1053: Insecure crypto for storing passwords

> An attacker can recover cached usernames and passwords due to insecure cryptographic storage in the remote-login-service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-93m4-r4xc-vhfw

## What is CVE-2013-1053?

CVE-2013-1053 is a medium-severity vulnerability in Canonical remote-login-service, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In crypt.c of remote-login-service, the cryptographic algorithm used to cache usernames and passwords is insecure. An attacker could use this vulnerability to recover usernames and passwords from the file. This issue affects version 1.0.0-0ubuntu3 and prior versions.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm), CWE-261 (Weak Encoding for Password)

## Which versions are affected by CVE-2013-1053?

It affects 1 product.


Products: Canonical Remote-Login-Service.

## How do I fix CVE-2013-1053?

No fix has been published for CVE-2013-1053 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-1053 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1053 and fix it if it is affected.

What it is: CVE-2013-1053 is a medium-severity vulnerability in Canonical remote-login-service, published on 13 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1053 in the wild and no public exploit code.

Affected product: Canonical remote-login-service. 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-2013-1053/ (Markdown: https://insights.sbomify.com/CVE-2013-1053/index.md)
```

## Sources

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

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