CVE-2012-6352
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 · uneditedThe Session Manager in IBM Sterling Connect:Direct through 4.1.0.3 on UNIX allows remote attackers to cause a denial of service (daemon crash and disk consumption) via crafted data.
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 confidenceThe Session Manager component in IBM Sterling Connect:Direct versions through 4.1.0.3 on UNIX platforms contains a vulnerability where remote attackers can send specially crafted data packets to cause the daemon to crash and consume disk space, resulting in denial of service.
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= 4.1.0.0= 4.1.0.1= 4.1.0.2= 4.1.0.3CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 the installed version of IBM Sterling Connect:DirectRun the command that displays the Connect:Direct version (typically 'cdver' or check the installation directory for version files). Compare the output to the affected range 4.1.0.0 through 4.1.0.3.Affected if The installed version is 4.1.0.0, 4.1.0.1, 4.1.0.2, or 4.1.0.3 on a UNIX platform.
-
Confirm the operating system platformRun 'uname -a' or 'oslevel' to verify the system is a UNIX variant (AIX, Solaris, Linux, HP-UX).Affected if The system is running any UNIX operating system.
-
Determine if the Session Manager component is enabledCheck the Connect:Direct configuration for Session Manager settings, typically found in the initialization parameters or configuration files. Look for 'Session Manager' or 'SMGR' entries.Affected if The Session Manager component is enabled and running.
-
Locate the Session Manager port configurationExamine the Connect:Direct configuration files or run commands to display network port bindings. Session Manager typically uses a specific TCP port (commonly 1364, but verify in your configuration).Affected if A Session Manager listener port is configured and active.
-
Review disk space usage in the Connect:Direct directoriesCheck for unusual growth in log directories, particularly in areas where crash dumps or error logs are written. Use 'df -h' on Connect:Direct filesystem mount points and 'du -sh' on log directories.Affected if Disk consumption is abnormally high in Connect:Direct data or log directories.
You are affected if IBM Sterling Connect:Direct version 4.1.0.0, 4.1.0.1, 4.1.0.2, or 4.1.0.3 is installed on a UNIX system with the Session Manager component enabled and network 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 dataUpgrade to a version beyond 4.1.0.3 when available. In the interim, restrict network access to the Connect:Direct Session Manager port using firewalls or access control lists, and implement disk monitoring alerts to detect unusual consumption.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6352 — 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-6352 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