CVE-2012-2163
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 Scale Out Network Attached Storage (SONAS) 1.1 through 1.3.1 allows remote authenticated administrators to execute arbitrary Linux commands via the (1) Command Line Interface or (2) Graphical User Interface, related to a "code injection" issue.
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 SONAS versions 1.1-1.3.1 contains a code injection vulnerability in both the CLI and GUI interfaces that allows remote authenticated administrators to execute arbitrary Linux commands on the underlying operating 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= 1.1= 1.3.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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/A:C
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 if the system is IBM SONASRun the command 'lsb_release -a' or check /etc/issue for IBM SONAS identification strings. Alternatively, run 'uname -a' and look for SONAS-specific kernel or system identifiers.Affected if The system is confirmed to be IBM SONAS Scale Out Network Attached Storage.
-
Determine the installed SONAS versionRun the command 'sonasversion' if available, or check /opt/IBM/sonas/version for the version file. Compare the discovered version against the affected range 1.1 to 1.3.1.Affected if The installed version falls within 1.1 through 1.3.1 inclusive.
-
Verify if GUI administrative interface is accessibleCheck if the GUI service is running and exposed by reviewing running processes (ps aux | grep -i gui) or checking network listeners (netstat -tlnp) on ports typically used for the SONAS web interface.Affected if The GUI administrative interface is running and network-accessible.
-
Verify if CLI administrative interface is accessibleCheck if the CLI service is running and accessible by reviewing running processes (ps aux | grep -i cli) or checking SSH/network access to the administrative CLI port.Affected if The CLI administrative interface is running and network-accessible.
The system is affected if it is IBM SONAS version 1.1 through 1.3.1 and has either the GUI or CLI administrative interface accessible to network attackers, allowing authenticated administrators to inject arbitrary commands.
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 SONAS or upgrade to a patched version; implement strict access controls for administrative interfaces and monitor for suspicious administrative activity.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2163 — 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-2163 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