CVE-2013-0560
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 · uneditedMultiple SQL injection vulnerabilities in IBM Sterling B2B Integrator 5.1 and 5.2 and Sterling File Gateway 2.1 and 2.2 allow remote authenticated users to execute arbitrary SQL commands via unspecified vectors, a different vulnerability than CVE-2012-5766.
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 confidenceMultiple SQL injection vulnerabilities in IBM Sterling B2B Integrator 5.1/5.2 and Sterling File Gateway 2.1/2.2 allow remote authenticated users to execute arbitrary SQL commands via unspecified vectors in the application layer.
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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/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 B2B Integrator installationLocate the installation directory and check for version.txt or use the platform's version command if available. Common paths include /opt/IBM/SterlingB2BIntegrator or C:\IBM\SterlingB2BIntegrator on Windows.Affected if The installed version is exactly 5.1 or 5.2
-
Identify IBM Sterling File Gateway installationLocate the installation directory and check for version information. Common paths include /opt/IBM/SterlingFileGateway or check within the B2B Integrator installation if deployed as a combined platform.Affected if The installed version is exactly 2.1 or 2.2
-
Verify application is network accessibleConfirm the web interface or API endpoints are exposed to network users. Check firewall rules and application server bindings (typically on ports 8443, 443, or 8080).Affected if The application interface is reachable from untrusted networks without proper network segmentation
-
Confirm authentication mechanisms are activeReview whether user authentication is enabled for the application. SQL injection in this CVE requires authenticated access, so check if user accounts exist and login functionality is operational.Affected if User authentication is enabled and user accounts are provisioned in the system
You are affected if IBM Sterling B2B Integrator version 5.1 or 5.2, or Sterling File Gateway version 2.1 or 2.2 is installed and the application is accessible to authenticated users.
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 dataRemediate by upgrading to patched versions (IBM Sterling B2B Integrator 5.2.6+ and Sterling File Gateway 2.2.3+) or applying IBM interim fixes; additionally review and harden input validation across all user-facing interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0560 — 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-0560 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