CVE-2013-0494
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 · uneditedIBM Sterling B2B Integrator 5.0 and 5.1 allows remote attackers to cause a denial of service (memory and CPU consumption) via a crafted HTTP (1) Range or (2) Request-Range header.
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 confidenceIBM Sterling B2B Integrator versions 5.0 and 5.1 are vulnerable to a denial of service attack via crafted HTTP Range or Request-Range headers. These specially crafted headers cause excessive memory and CPU consumption on the affected system.
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.0= 5.1CVSS 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.
-
Locate IBM Sterling B2B Integrator installationSearch for the installation directory - typical paths include /opt/ibm/SterlingB2B or C:\ibm\SterlingB2B on Windows, or check for the 'SBI' or 'SterlingB2B' directory in standard installation locations.Affected if The product is found installed on the system.
-
Determine installed versionCheck for a version file or manifest within the installation directory. Common indicators include a 'version.txt', 'release.info' file, or examine the installation metadata. The product may also expose version information via its web interface or configuration files.Affected if The version cannot be determined or is not clearly documented.
-
Compare version against affected releasesIf a version is identified, compare it exactly to 5.0 or 5.1. Note that partial updates or patch releases may be listed as 5.0.x or 5.1.x variants.Affected if The installed version is 5.0 or 5.1 exactly, including any point releases of these major versions.
-
Verify HTTP services are accessibleConfirm that the web-based services or API endpoints of Sterling B2B Integrator are exposed and reachable. This typically involves checking if the admin console or integration services port (often 8443 or 443) is listening.Affected if HTTP/HTTPS services are active and accept incoming connections.
A user is affected if IBM Sterling B2B Integrator version 5.0 or 5.1 is installed and its HTTP services are accessible, as the vulnerability is triggered by malformed Range headers on these web interfaces.
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 a patched version of IBM Sterling B2B Integrator (version 5.2 or later) or apply the relevant security patch from IBM. Consider implementing Web Application Firewall (WAF) rules to filter malformed Range headers as an interim measure.
- Consultation3.0 h
- Implementation6.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 $4,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0494 — 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-2013-0494 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