Security readout for executives and security teams
Plain-English summary
This flaw can allow IBM Sterling Connect:Direct for OpenVMS to use an unencrypted TCP/IP session even when SSL encryption is configured. That creates a risk that file-transfer data expected to be protected could move in cleartext. The public record does not provide CVSS scoring, observed exploitation, or detailed impact.
Executive priority
Treat this as a targeted legacy-platform confidentiality risk. Escalate if the affected product handles regulated, customer, financial, or operationally sensitive transfers, but do not assume active exploitation from the provided evidence.
Technical view
Affected server deployments may fail to reject client requests for unencrypted sessions when configured for SSL encryption with the client. The CVE lists IBM Sterling Connect:Direct for OpenVMS versions 3.4.00, 3.4.01, 3.5.00, 3.6.0, and 3.6.0.1. Impact is described only as unspecified.
Likely exposure
Exposure is likely limited to organizations still running the listed IBM Sterling Connect:Direct for OpenVMS versions as TCP/IP servers with SSL expected between client and server.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, proof-of-concept details, or active exploitation reporting. The attacker condition given is remote, but impact details are unspecified.
Researcher notes
Key unknowns are CVSS, exact impact, fix version, and exploitation status. Analysis should stay bounded to the named OpenVMS versions and SSL-enforced TCP/IP server scenario until IBM source details are reviewed.
Mitigation direction
- Check IBM PSIRT and X-Force guidance for supported remediation or configuration direction.
- Inventory OpenVMS Connect:Direct servers and confirm listed versions are absent or addressed.
- Review SSL enforcement settings for server-side TCP/IP sessions.
- Prioritize compensating controls around sensitive transfer paths until vendor guidance is confirmed.
Validation and detection
- Identify all IBM Sterling Connect:Direct for OpenVMS deployments and versions.
- Confirm whether each server is configured for SSL-encrypted client sessions.
- Review transfer logs for unexpected non-SSL or cleartext session negotiation.
- Validate remediation status against IBM’s advisory or X-Force entry.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2013-4035 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- scd-cve20134035-weak-security(86138)CVE reference · vdb-entry, x_refsource_XF
- https://www.ibm.com/blogs/psirt/security-bulletin-ibm-sterling-connectdirect-for-openvms-unencrypted-data-transfers-can-occur-even-when-ssl-encryption-is-specified-in-the-security-configuration-cve-2013-4035/CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.