dbcve.org
OpenlitespeedApplication · Litespeedtech

CVE-2015-3890

HIGH · 7.5 CVSS v3.1 Published 2017-09-20
Fix available
A fix is available. Upgrade to 1.3.10 or later.
See remediation →
84/100
Remediation priority · High
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
Use-after-free vulnerability in Open Litespeed before 1.3.10.

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

Use-after-free vulnerability in Open Litespeed web server versions prior to 1.3.10. This memory corruption flaw could allow remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors.

MitigationUpgrade Open Litespeed to version 1.3.10 or later to address the use-after-free vulnerability.

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
OpenlitespeedApplication
Affected:< 1.3.10

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
None
Integrity
None
Availability
High

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

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. Locate Open Litespeed installation
    Check common installation paths such as /usr/local/lsws/ or /opt/lsws/, or search for the 'lshttpd' or 'litespeed' binary using 'which lshttpd' or 'which litespeed'
    Affected if Open Litespeed is installed on the system
  2. Determine installed version
    Run the binary with version flag (such as 'litespeed -v' or 'lshttpd -v') or check the RELEASE file in the installation directory, or query via package manager (rpm -q openlitespeed or dpkg -l openlitespeed)
    Affected if Version information is returned
  3. Compare against vulnerable range
    Compare the installed version number to 1.3.10 using semantic version comparison
    Affected if Installed version is 1.3.9 or lower, or any version starting with 1.3.x where x is less than 10
  4. Verify service is running and exposed
    Check if the Open Litespeed process is running and listening on configured ports (commonly 80, 443, or 7080 for the management interface)
    Affected if Service is actively running and network-accessible

The environment is affected if Open Litespeed is installed with a version lower than 1.3.10 and the service is running

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 1.3.10 or later
Fixed in 1.3.10
Interim mitigation

Upgrade Open Litespeed to version 1.3.10 or later to address the use-after-free vulnerability.

Fix this in Openlitespeed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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