CVE-2014-6199
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 · uneditedThe HTTP Server Adapter in IBM Sterling B2B Integrator 5.1 and 5.2.x and Sterling File Gateway 2.1 and 2.2 allows remote attackers to cause a denial of service (connection-slot exhaustion) via a crafted HTTP request.
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 · moderate confidenceThe HTTP Server Adapter in IBM Sterling B2B Integrator 5.1/5.2.x and Sterling File Gateway 2.1/2.2 contains a denial of service vulnerability where crafted HTTP requests can exhaust available connection slots, preventing legitimate users from accessing the service.
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.1= 5.2= 5.2.1= 5.2.2= 5.2.4= 5.2.4.1= 5.2.4.2= 5.2.5.0= 2.1= 2.2CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 IBM Sterling product installationLook for installation directories or running processes. Check for 'Sterling B2B Integrator' or 'Sterling File Gateway' processes or services on the system.Affected if Either IBM Sterling B2B Integrator or Sterling File Gateway is installed and running.
-
Determine installed product versionCheck the version of the installed IBM Sterling product. Common locations include installation logs, version files in the installation directory, or the product's admin interface.Affected if The version matches 5.1, 5.2, 5.2.1, 5.2.2, 5.2.4, 5.2.4.1, 5.2.4.2, or 5.2.5.0 for Sterling B2B Integrator; or 2.1 or 2.2 for Sterling File Gateway.
-
Verify HTTP Server Adapter is enabledCheck if the HTTP Server Adapter component is enabled and running. This is typically configured in the product's admin console or configuration files.Affected if HTTP Server Adapter is enabled and listening for HTTP connections.
-
Inspect HTTP Server Adapter configurationLocate and review the HTTP Server Adapter configuration file or settings. Look for connection limit, timeout, and pool settings if exposed.Affected if HTTP Server Adapter is in use with no connection limits configured or limits set very high.
-
Monitor for connection exhaustion symptomsCheck current network connections to the HTTP Server Adapter port. Use commands like 'netstat' to see established connections, or review server logs for connection-related errors.Affected if A large number of connections are observed in TIME_WAIT or ESTABLISHED state, or logs show connection failures.
A user is affected if they have IBM Sterling B2B Integrator versions 5.1 through 5.2.5.0 or Sterling File Gateway versions 2.1 or 2.2 running with the HTTP Server Adapter enabled and exposed to network requests.
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 dataImplement connection pool limits, request timeouts, and rate limiting on the HTTP Server Adapter; apply vendor patches if available; consider placing a reverse proxy or WAF in front to filter malicious requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6199 — 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-6199 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