dbcve.org
Last.fm DesktopApplication · Last.fm

CVE-2019-19251

MEDIUM · 5.3 CVSS v3.1 Published 2019-12-10
Fix available
A fix is available. Upgrade to after 2.1.39 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
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.

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 · high confidence

The Last.fm Scrobbler desktop app version 2.1.39 and earlier on macOS transmits API keys over unencrypted HTTP connections. Although an 'Enable SSL' option exists within the application, it is disabled by default, resulting in cleartext transmission of sensitive API credentials immediately upon app startup.

MitigationEnable the built-in SSL/TLS option in the application settings, or update the default configuration to have SSL enabled by default to prevent credential exposure.

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
Last.fm DesktopApplication
Affected:<= 2.1.39

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check installed Last.fm Desktop version
    Locate the Last.fm Desktop application in /Applications. Right-click the app and select 'Get Info' to view the version number displayed as 'Version: X.X.X'
    Affected if Version is 2.1.39 or earlier
  2. Verify SSL option state in application settings
    Launch Last.fm Desktop and open Settings. Look for a connection or network settings section containing an 'Enable SSL' or 'Use HTTPS' checkbox
    Affected if The SSL option is unchecked (disabled)
  3. Inspect application configuration file
    Examine the application configuration stored in the user's application support directory, typically found in ~/Library/Application Support/Last.fm/ or similar location. Look for a setting such as EnableSSL, UseHTTPS, or a similar flag controlling encrypted connections
    Affected if The configuration file shows SSL/TLS is disabled or not set to enabled

User is affected if running Last.fm Desktop version 2.1.39 or earlier with the SSL option disabled, causing API credentials to be transmitted in cleartext over HTTP.

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 2.1.39
Interim mitigation

Enable the built-in SSL/TLS option in the application settings, or update the default configuration to have SSL enabled by default to prevent credential exposure.

Fix this in Last.fm Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-19251 — 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-2019-19251 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