# CVE-2019-19251: Weak cryptography in n/a

> The Last.fm desktop app transmits API keys over unencrypted HTTP by default, allowing attackers to intercept sensitive credentials.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c686-g9ff-6f7m

## What is CVE-2019-19251?

CVE-2019-19251 is a medium-severity vulnerability in n/a, published on 10 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Last.fm desktop app (Last.fm Scrobbler) through 2.1.39 on macOS makes HTTP requests that include an API key without the use of SSL/TLS. Although there is an Enable SSL option, it is disabled by default, and cleartext requests are made as soon as the app starts.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Last.fm Last.fm Desktop.

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

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

## Is CVE-2019-19251 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19251 is a medium-severity vulnerability in n/a, published on 10 Dec 2019. 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-19251 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-19251/ (Markdown: https://insights.sbomify.com/CVE-2019-19251/index.md)
```

## Sources

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

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