dbcve.org
SoliddbApplication · Ibm

CVE-2011-1560

HIGH · 9.3 CVSS v2.0 Published 2011-04-05
Fix available
A fix is available. Upgrade to after 4.5.180 or later.
See remediation →
100/100
Remediation priority · Urgent
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
solid.exe in IBM solidDB before 4.5.181, 6.0.x before 6.0.1067, 6.1.x and 6.3.x before 6.3.47, and 6.5.x before 6.5.0.3 uses a password-hash length specified by the client, which allows remote attackers to bypass authentication via a short length value.

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

IBM solidDB's solid.exe uses a client-specified password-hash length during authentication, without proper server-side validation. An attacker can exploit this by sending a short length value to bypass authentication entirely and gain unauthorized access to the database.

MitigationUpgrade to solidDB version 4.5.181, 6.0.1067, 6.3.47, or 6.5.0.3 or later, which contain the fix for proper server-side validation of password-hash length.

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
SoliddbApplication
Affected:<= 4.5.180= 4.5.167= 4.5.168= 4.5.169= 4.5.173= 4.5.175= 4.5.176= 4.5.178= 4.5.179= 6.0.1060= 6.0.1061= 6.0.1064

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 solidDB installation and version
    Check for solid.exe in installation directories (commonly C:\IBM\soliddb or /opt/ibm/soliddb) and run 'solid.exe -v' or check version from installation metadata
    Affected if Version matches any of: 4.5.167, 4.5.168, 4.5.169, 4.5.173, 4.5.175, 4.5.176, 4.5.178, 4.5.179, 4.5.180, or any 6.0.x version below 6.0.1067 (including 6.0.1060, 6.0.1061, 6.0.1064)
  2. Identify solidDB server listening ports
    Run 'netstat -an | findstr 1314' or 'netstat -tulpn | grep solid' to find ports where solid.exe listens (default port 1314 for solidDB)
    Affected if solidDB server is listening on a network-accessible port
  3. Verify authentication is enabled
    Inspect solidDB configuration files (soliddb.ini in the data directory) for authentication settings such as PASSWORD_HASH_LENGTH or authentication-related parameters
    Affected if Authentication settings are present and the server accepts remote connections
  4. Check network exposure
    Review firewall rules and network segmentation to determine if the solidDB port (default 1314) is exposed to untrusted networks
    Affected if Port 1314 or the configured solidDB port is accessible from untrusted networks

You are affected if solidDB is running a version between 4.5.167-4.5.180 or 6.0.1060-6.0.1064 and is accessible over the network, allowing an attacker to send specially crafted authentication packets with manipulated password-hash length values.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.5.180
Interim mitigation

Upgrade to solidDB version 4.5.181, 6.0.1067, 6.3.47, or 6.5.0.3 or later, which contain the fix for proper server-side validation of password-hash length.

Recommended fix High confidence

IBM solidDB 4.5.181 (for 4.5.x), 6.0.1067 (for 6.0.x), 6.3.47 (for 6.1.x/6.3.x), or 6.5.0.3 (for 6.5.x) - choose the appropriate fixed version for your branch

  1. 1. Identify the current IBM solidDB version by checking the solid.exe file version or running 'solid -v'
  2. 2. Determine which branch (4.5.x, 6.0.x, 6.1.x, 6.3.x, or 6.5.x) is currently in use
  3. 3. Backup all solidDB databases and configuration files before proceeding
  4. 4. Stop the solidDB service or process
  5. 5. Download the fixed version from IBM (4.5.181 for 4.5.x branch, 6.0.1067 for 6.0.x, 6.3.47 for 6.1.x/6.3.x, or 6.5.0.3 for 6.5.x) from IBM Fix Central or the IBM software repository
  6. 6. Install the upgraded solidDB version following IBM's installation documentation
  7. 7. Restore the database files and configuration to the new installation
  8. 8. Start the solidDB service
Caveat Upgrading solidDB across major version branches (e.g., 4.5 to 6.x) may require database migration and could have compatibility impacts on existing applications; test thoroughly in a non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Soliddb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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