StrongholdApplication · Redhat
CVE-2001-0868
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 · uneditedRed Hat Stronghold 2.3 to 3.0 allows remote attackers to retrieve system information via an HTTP GET request to (1) stronghold-info or (2) stronghold-status.
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 confidenceRed Hat Stronghold 2.3 through 3.0 contains an information disclosure vulnerability where remote attackers can retrieve sensitive system information via HTTP GET requests to the /stronghold-info or /stronghold-status endpoints. These endpoints expose system details without authentication.
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
StrongholdApplication
<= 3.0= 2.3CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Red Hat Stronghold is installedCheck for the presence of Stronghold by looking for its installation directory, typically under /usr/local/stronghold or /var/stronghold, or by checking the server banner via: `telnet <server> 80` and sending `HEAD / HTTP/1.0` then pressing Enter twiceAffected if Stronghold web server is present on the system
-
Determine the installed Stronghold versionCheck the version string in the server banner response from step 1, or look for a version file in the Stronghold installation directory, commonly found in the 'conf' or 'lib' directoryAffected if The version number returned is 2.3 or falls within the range greater than 2.3 up to and including 3.0
-
Verify if vulnerable endpoints are accessibleSend an HTTP GET request to http://your-server/stronghold-info and http://your-server/stronghold-status using curl or a browser, without providing any authentication credentialsAffected if Either endpoint returns system information such as server configuration, paths, or status details without prompting for login
-
Check web server access control configurationExamine the Stronghold configuration files (httpd.conf or .htaccess) for any Allow/Deny rules or authentication requirements applied to the /stronghold-info and /stronghold-status pathsAffected if No IP restrictions or authentication requirements are defined for these endpoints, meaning they are accessible to any remote user
If Stronghold versions 2.3 through 3.0 are running and the /stronghold-info or /stronghold-status endpoints respond without authentication, the system is affected by this information disclosure vulnerability.
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 dataRestrict access to the /stronghold-info and /stronghold-status endpoints through web server access controls (IP restrictions, authentication requirements) or upgrade to a patched version if available.
Fix this in Stronghold
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0868 — 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-2001-0868 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