IBM Sterling Connect:Direct
CVE-2025-36137
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as privileged CCD user
-
DeliveryTrigger maintenance/post-update script task
-
ExploitAbuse unnecessary script privileges
-
ExecutionExecute commands at elevated privilege
-
ImpactFull compromise of Connect:Direct node
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V8 - Authorization Unnecessary privilege execution
|
| Exploitation Conditions | Exploitation requires an authenticated Control Center Director (CCD) user account (PR:H) on an affected Sterling Connect:Direct for UNIX node, and depends on the product's maintenance-task / post-update script workflow that is granted more privileges than necessary. The limiting factors are substantial: the attacker must already hold a privileged CCD role, no path exists for an unauthenticated or low-privilege outsider, and the flaw is tied to the maintenance/post-update-script code path rather than a default runtime feature. Affected versions are 6.2.0.7 through 6.2.0.9 iFix004, 6.3.0.2 through 6.3.0.5 iFix002, and 6.4.0.0 through 6.4.0.2 iFix001; other versions are not in scope. |
| Impact | This is a privilege-escalation flaw (CWE-250, Execution with Unnecessary Privileges) in IBM Sterling Connect:Direct for UNIX, and the signals point to a real-but-bounded local administration risk rather than an urgent mass-exploitation threat. The published CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N, C:H/I:H/A:H, score 7.2) already requires high privileges (PR:H), meaning the attacker must be an authenticated, already-privileged Control Center Director (CCD) user before any escalation is possible - this is the dominant limiting factor. No EPSS score was provided in the input, the CVE is not listed in CISA KEV, and no public exploit code is referenced, so there is no public exploit identified at time of analysis. CONFLICTING SIGNAL: the CVSS vector asserts AV:N (network), yet the description describes a privileged CCD user abusing permissions assigned for local maintenance tasks / post-update scripts, which reads as local-to-the-managed-host escalation - verify the true attack vector with IBM, as AV:N may reflect the fact that CCD administration is performed over the network. Net: a legitimately high-severity integrity/confidentiality/availability issue for organizations running the affected versions, but gated behind existing privileged access, so it is a patch-in-normal-cycle priority absent any evidence of active exploitation. |
| Exploit ScenarioDerived | An already-privileged Control Center Director (CCD) user who should be constrained to maintenance duties leverages the unnecessary privileges granted to post-update scripts to run commands at a higher privilege level than intended, gaining full control over the Connect:Direct for UNIX node. Because exploitation requires existing high-privilege CCD access (PR:H) and no user interaction, a malicious or compromised administrator (or a lower-trust operator who should not have had this capability) is the realistic threat actor. No public proof-of-concept is referenced in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Privilege escalation in IBM Sterling Connect:Direct for UNIX allows an already-privileged Control Center Director (CCD) user to gain further privileges because the product assigns unnecessary permissions to maintenance tasks and post-update scripts (CWE-250). Affected builds are 6.2.0.7 through 6.2.0.9 iFix004, 6.3.0.2 through 6.3.0.5 iFix002, and 6.4.0.0 through 6.4.0.2 iFix001 on UNIX; exploitation requires an authenticated CCD account with a high-privilege role (CVSS PR:H) and access to the maintenance/post-update-script workflow, so no unauthenticated or low-privilege outsider path exists. There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV); NVD scores it 7.2 (AV:N) while our independent assessment rates the practical vector as local (AV:L) given the required privileged local/admin foothold.
RemediationAI
Apply the vendor fix for your Sterling Connect:Direct for UNIX line as published in the IBM advisory at https://www.ibm.com/support/pages/node/7249678, which is the authoritative source for the exact patched build or iFix level for the 6.2.0.x, 6.3.0.x, and 6.4.0.x branches; the input data does not enumerate a specific fix version, so confirm the target build against that advisory rather than assuming one. Because exploitation requires an already-privileged CCD account, the most effective compensating control is to tightly restrict and audit who holds Control Center Director maintenance privileges and to treat those accounts as tier-0, accepting the operational trade-off that routine maintenance will require more controlled, possibly break-glass, access. Review and constrain the permissions inherited by post-update/maintenance scripts on the UNIX node so they run with only the privileges they need (the direct mitigation for the CWE-250 root cause), recognizing that hand-tuning script permissions risks breaking automated updates and must be revalidated after each vendor update. Additionally, limit network exposure of the CCD/Connect:Direct administrative interfaces to trusted management networks, and monitor for unexpected privilege changes or maintenance-task invocations by CCD users; this reduces reachability but does not remove the underlying privilege misassignment and should be viewed as defense in depth only.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-250, Execution with Unnecessary Privileges: IBM Sterling Connect:Direct for UNIX grants Control Center Director (CCD) users rights over maintenance tasks that exceed what those tasks legitimately need, and the post-update scripts that perform those maintenance operations inherit that over-broad privilege context. Because the scripts run with more authority than the maintenance function requires, a CCD user who is already privileged can leverage that misassignment to elevate to a higher privilege level on the node. The CPE data confirms the scope is the UNIX build of Sterling Connect:Direct across three maintenance lines (6.2.0.x, 6.3.0.x, 6.4.0.x) with specific iFix levels, so deployments on other platforms or unpinned builds are not in scope. The privilege boundary that is crossed is intra-product (CCD maintenance role to a stronger role on the UNIX host), not the network perimeter: the NVD vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) treats the attack as network-reachable, while our independent assessment constrains it to a local vector (AV:L) because the attacker must already hold an authenticated, high-privilege CCD account and operate through the product's maintenance/post-update workflow. Confidentiality, integrity, and availability impacts are all rated High, consistent with a privileged user obtaining control over host-level operations.
Know when Sterling Connect gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Escalation via locally-executed maintenance/post-update scripts by an existing privileged CCD user implies AV:L and PR:H; full node compromise yields C:H/I:H/A:H.
Primary rating from Vendor (us).
CVSS VectorVendor: us
DescriptionCVE.org
IBM Sterling Connect Direct for Unix 6.2.0.7 through 6.2.0.9 iFix004, 6.4.0.0 through 6.4.0.2 iFix001, and 6.3.0.2 through 6.3.0.5 iFix002 incorrectly assigns permissions for maintenance tasks to Control Center Director (CCD) users that could allow a privileged user to escalate their privileges further due to unnecessary privilege assignment for post update scripts.
Executive ViewAI
IBM Sterling Connect:Direct for UNIX builds 6.2.0.7 through 6.2.0.9 iFix004, 6.3.0.2 through 6.3.0.5 iFix002, and 6.4.0.0 through 6.4.0.2 iFix001 contain a high-severity privilege-escalation issue that could allow an authenticated high-privilege Control Center Director user to gain additional rights over maintenance and post-update workflows. Because exploitation requires an already privileged CCD account on these UNIX builds, the immediate risk is concentrated among teams managing these file-transfer services rather than external actors, but leadership should still prioritize privileged-access review and interim controls. No vendor-released patch identified at time of analysis and no public exploit identified at time of analysis.
Restrict access to maintenance/post-update-script workflow to only necessary high-privilege CCD accounts; remove unnecessary permissions from maintenance tasks and post-update scripts (CWE-250); enforce least privilege and separation of duties; monitor privileged CCD activity and script changes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Affected Products (CPE)CVE.org
More in Sterling Connect
View allIBM Sterling Connect:Direct for UNIX 4.2.0, 4.3.0, 6.0.0, and 6.1.0 is vulnerable to a stack based buffer ovreflow, caus
IBM Sterling Connect:Direct Web Services 1.0 and 6.0 uses weaker than expected cryptographic algorithms that could allow
IBM Sterling Connect:Direct Web Services 1.0 and 6.0 uses an inadequate account lockout setting that could allow a remot
IBM Sterling Connect Direct for Microsoft Windows 4.7, 4.8, 6.0, and 6.1 could allow a remote attacker to cause a denial
The file-copying functionality in IBM Sterling Connect:Direct 3.8.00, 4.0.00, and 4.1.0 for UNIX on AIX 6.1 through 7.1
IBM Sterling Connect:Express for UNIX 1.5 is vulnerable to server-side request forgery (SSRF). Rated medium severity (CV
IBM Sterling Connect:Express for UNIX 1.5 browser UI is vulnerable to attacks that rely on the use of cookies without th
The Session Manager in IBM Sterling Connect:Direct through 4.1.0.3 on UNIX allows remote attackers to cause a denial of
IBM Sterling Connect:Direct 4.5.00, 4.5.01, 4.6.0 before 4.6.0.6 iFix008, and 4.7.0 before 4.7.0.4 on Windows allows loc
IBM Sterling Connect:Direct for Unix 4.1.0 before 4.1.0.4 iFix073 and 4.2.0 before 4.2.0.4 iFix003 uses default file per
IBM Sterling Connect:Direct 4.5.00, 4.5.01, 4.6.0 before 4.6.0.6 iFix008, and 4.7.0 before 4.7.0.4 on Windows allows loc
IBM Sterling Connect:Express for Microsoft Windows 3.1.0.0 through 3.1.0.22 uses an inadequate account lockout setting t
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB