CVE-2012-5766
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 vectors involving the RNVisibility page and unspecified screens, a different vulnerability than CVE-2013-0560.
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 confidenceSQL injection vulnerabilities in IBM Sterling B2B Integrator and Sterling File Gateway allow authenticated users to execute arbitrary SQL commands through the RNVisibility page and unspecified screens. The vulnerabilities stem from improper input validation in web interface parameters that are passed to database queries.
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 product and versionLocate the installed IBM Sterling B2B Integrator or Sterling File Gateway installation directory and check the version file or about page. Common locations include the installation root directory or the web application's login page which often displays version information.Affected if The installed version matches 5.1 or 5.2 for Sterling B2B Integrator, or 2.1 or 2.2 for Sterling File Gateway
-
Confirm web interface is accessibleVerify that the Sterling web interface (typically accessed via HTTP/HTTPS on ports 8080, 8443, or similar) is running and reachable. Check if the login portal is available.Affected if The web interface is exposed and the product version is one of the affected versions listed above
-
Locate the RNVisibility pageCheck if the RNVisibility servlet or JSP page is present within the web application. This is typically found under the web application's path, often in directories related to reporting or visibility features. Attempt to access a URL pattern such as /RNVisibility or similar paths containing 'visibility' in the application URL structure.Affected if The RNVisibility page or similar visibility-related endpoints are present in the affected version installations
-
Verify authentication mechanismConfirm that the application uses form-based or session-based authentication for web interface access. The SQL injection vulnerability requires an authenticated session, so verify that login functionality exists and is enforced.Affected if The web interface requires authentication and the product version matches the affected versions
A user is affected if they are running IBM Sterling B2B Integrator version 5.1 or 5.2, or Sterling File Gateway version 2.1 or 2.2, with the web interface and RNVisibility page 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 dataImplement parameterized queries or prepared statements for all database interactions, apply vendor patches when available, and perform input validation on all user-supplied parameters in affected screens.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5766 — 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-2012-5766 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