CVE-2014-5504
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 · uneditedSolarWinds Log and Event Manager before 6.0 uses "static" credentials, which makes it easier for remote attackers to obtain access to the database and execute arbitrary code via unspecified vectors, related to HyperSQL.
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 confidenceSolarWinds Log and Event Manager versions before 6.0 contain hardcoded static credentials embedded in the software that allow unauthenticated remote attackers to access the HyperSQL database and execute arbitrary code. The vulnerability stems from the use of static credentials for database connections that cannot be changed by administrators.
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<= 5.7.0= 5.2.0= 5.4.0= 5.5.0= 5.6.0CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SolarWinds LEM versionOpen Windows Programs and Features (appwiz.cpl) or check the SolarWinds installation directory for version information filesAffected if The version shown is 5.2.0, 5.4.0, 5.5.0, 5.6.0, or any version 5.7.0 or lower
-
Locate HyperSQL database configurationBrowse the SolarWinds Log and Event Manager installation directory (typically C:\Program Files\SolarWinds\Log and Event Manager or similar) for HyperSQL configuration files or database connection configurationAffected if Configuration files containing hardcoded database credentials are present and readable
-
Verify HyperSQL port exposureOpen a command prompt and run 'netstat -an | findstr 9001' or use a port scanner to check if port 9001 (default HyperSQL port) is listening on external interfacesAffected if Port 9001 or the HyperSQL service port is listening on 0.0.0.0 or an external IP address rather than only localhost (127.0.0.1)
Your environment is affected if SolarWinds Log and Event Manager version is 5.7.0 or lower and the HyperSQL database with its hardcoded credentials is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to SolarWinds Log and Event Manager version 6.0 or later to eliminate the static credential vulnerability. If immediate upgrade is not possible, network segmentation and firewall rules should be applied to restrict access to the affected system.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-5504 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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