dbcve.org
LitestreamApplication

CVE-2024-41254

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-31
Fix available
A fix is available. Upgrade to after 0.3.13 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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
An issue was discovered in litestream v0.3.13. The usage of the ssh.InsecureIgnoreHostKey() disables host key verification, possibly allowing attackers to obtain sensitive information via a man-in-the-middle attack.

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

In litestream v0.3.13, the SSH client configuration uses ssh.InsecureIgnoreHostKey() which explicitly disables host key verification. This allows a man-in-the-middle attacker to impersonate the SSH server and intercept or modify sensitive data in transit.

MitigationReplace ssh.InsecureIgnoreHostKey() with proper host key verification using a custom HostKeyCallback that validates the server's host key against a known set or stores verified keys.

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
LitestreamApplication
Affected:<= 0.3.13

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Identify Litestream version
    Run `litestream --version` or check the installed binary version
    Affected if Version is 0.3.13 or lower
  2. Check for SSH destination configuration
    Examine your litestream.yml or litestone.toml configuration file for any `ssh:` sections or SSH-related destination settings
    Affected if SSH destinations are configured in the configuration file
  3. Verify SSH client usage
    Review your configuration to confirm Litestream is connecting to remote replicas over SSH (for backup or restore operations)
    Affected if Litestream is configured to use SSH connections to remote servers
  4. Confirm vulnerable code presence
    Since the issue is in the SSH client code using ssh.InsecureIgnoreHostKey(), if you use Litestream <= 0.3.13 with SSH destinations, the insecure behavior is present in the binary itself
    Affected if Running Litestream version 0.3.13 or lower with active SSH destination configurations

You are affected if you are running Litestream version 0.3.13 or lower AND have configured SSH destinations for replica connections, as the SSH client will unconditionally accept any host key.

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

Replace ssh.InsecureIgnoreHostKey() with proper host key verification using a custom HostKeyCallback that validates the server's host key against a known set or stores verified keys.

Fix this in Litestream Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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