CVE-2013-2982
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 authenticated users to upload arbitrary files 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 confidenceIBM Sterling B2B Integrator 5.1/5.2 and Sterling File Gateway 2.1/2.2 contain an arbitrary file upload vulnerability allowing remote authenticated users to upload files to arbitrary locations on the system, potentially leading to remote code execution if files are placed in web-accessible directories.
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 installed IBM Sterling product and versionLocate the product installation directory and check version files or use product-specific version query commands. Common locations include installation logs, version.properties files, or the administration console version display.Affected if The installed product is IBM Sterling B2B Integrator version 5.1 or 5.2, or IBM Sterling File Gateway version 2.1 or 2.2
-
Determine if user authentication is enabled for the web interfaceCheck the authentication configuration settings in the Sterling administration console or configuration files. Verify whether login credentials are required for accessing file upload functionality.Affected if Authentication is enabled and users have access to file upload features, allowing authenticated users to exploit the arbitrary file upload flaw
-
Inspect web-accessible directories for unexpected uploaded filesReview directories accessible via the web server (such as web root, docroot, or publicly accessible URI paths) for unfamiliar files with suspicious extensions like .jsp, .php, .exe, or .sh.Affected if Unexpected executable or script files exist in web-accessible directories that were not intentionally placed there by administrators
-
Review file upload logs for suspicious activityExamine Sterling application logs, web server logs, and system audit logs for file upload requests that specify unusual target directories or file types, especially uploads targeting web root or system directories.Affected if Logs show file upload requests to non-standard directories or requests with directory traversal patterns in the filename field
You are affected if you are running Sterling B2B Integrator 5.1/5.2 or Sterling File Gateway 2.1/2.2 with authenticated file upload functionality enabled and have suspicious files in web-accessible locations.
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 strict server-side file type validation, restrict upload directories to non-executable paths, enforce least-privilege access controls on upload functionality, and apply vendor patches when available.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2982 — 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-2982 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