dbcve.org
Remote Login ServiceApplication · Canonical

CVE-2013-1053

MEDIUM · 5.5 CVSS v3.1 Published 2021-01-13
Fix available
A fix is available. Upgrade to after 1.0.0-0ubuntu3 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The remote-login-service cached user credentials (usernames and passwords) in a file using an insecure cryptographic algorithm in crypt.c. An attacker with file access could recover the plaintext credentials from the cached data.

MitigationReplace the insecure cryptographic algorithm with a modern, secure password hashing scheme (e.g., bcrypt, scrypt, or Argon2) and migrate existing cached credentials to the new format.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Remote Login ServiceApplication
Affected:<= 1.0.0-0ubuntu3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Canonical Remote Login Service package is installed
    Run `dpkg -l | grep remote-login-service` or check for the binary/service using `which remote-login-service` or `systemctl list-units | grep remote-login`
    Affected if The package is installed and its version is 1.0.0-0ubuntu3 or lower
  2. Identify the installed version number
    Run `dpkg -l remote-login-service` or check the package metadata with `apt-cache policy remote-login-service`
    Affected if The installed version is less than or equal to 1.0.0-0ubuntu3 (the vulnerable version)
  3. Locate the credential cache file
    Search for cached credential files in common locations such as `~/.cache/remote-login/`, `/var/cache/remote-login/`, or look for files matching patterns like `*credentials*`, `*auth*`, or `*.cached` in user home directories or /var
    Affected if A cached credential file exists in the expected storage location
  4. Inspect crypt.c source for insecure algorithm
    Locate the crypt.c source file in the package (typically in the source package under src/ or similar) and examine the encryption/hashing function used for storing credentials
    Affected if The code uses a weak or reversible encryption algorithm (such as simple XOR, base64 encoding without encryption, or a broken cipher) rather than a secure password hashing function like bcrypt, scrypt, or Argon2
  5. Check file permissions on credential cache
    Run `ls -la` on the credential cache file to verify permissions are overly permissive (e.g., world-readable or group-readable)
    Affected if The credential file has permissions allowing unauthorized users to read it (e.g., mode 644, 604, or any world-readable setting)

A user is affected if the Canonical Remote Login Service version is 1.0.0-0ubuntu3 or lower and a credential cache file using the insecure algorithm from crypt.c exists on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.0.0-0ubuntu3
Interim mitigation

Replace the insecure cryptographic algorithm with a modern, secure password hashing scheme (e.g., bcrypt, scrypt, or Argon2) and migrate existing cached credentials to the new format.

Fix this in Remote Login Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1053 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1053 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data