CVE-2013-0476
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.1 and 5.2 and Sterling File Gateway 2.1 and 2.2 allow remote attackers to inject arbitrary FTP commands via unspecified vectors.
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 confidenceCommand injection vulnerability in IBM Sterling B2B Integrator 5.1/5.2 and Sterling File Gateway 2.1/2.2 allows remote attackers to inject arbitrary FTP commands through unspecified vectors, potentially enabling unauthorized file operations or data exfiltration.
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= 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
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:P/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 the installed IBM Sterling productLocate the Sterling installation directory and check for product-specific files or registry entries that indicate whether Sterling B2B Integrator or Sterling File Gateway is installed. Look for product documentation or version files in the installation path.Affected if Neither product is installed, so the CVE does not apply.
-
Determine the installed product versionCheck the version information in the product's about page, version.txt file, or installation logs. For Sterling B2B Integrator, look for version 5.1 or 5.2. For Sterling File Gateway, look for version 2.1 or 2.2.Affected if The installed version is exactly 5.1 or 5.2 for Sterling B2B Integrator, or exactly 2.1 or 2.2 for Sterling File Gateway.
-
Verify if FTP services are enabledCheck the product configuration for FTP adapter, FTP gateway, or FTP transfer service settings. Look for active FTP listeners or adapters in the administration console or configuration files.Affected if FTP services are enabled and accessible, making the command injection vector possible.
-
Review FTP command handlers and adaptersExamine the configuration of FTP adapters or custom FTP handlers in the Sterling administration interface or configuration files. Look for any adapters that process external FTP commands.Affected if FTP adapters or command handlers are configured to accept and process commands from external sources.
The environment is affected only if IBM Sterling B2B Integrator version 5.1 or 5.2, or Sterling File Gateway version 2.1 or 2.2 is installed WITH FTP services enabled and 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 dataApply IBM patches for this vulnerability or upgrade to a supported version. Restrict network access to FTP services and implement input validation on FTP command handlers.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0476 — 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-0476 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