LiveActive security incident?Get immediate response
CVE Record

CVE-2011-1432: The STARTTLS implementation in SCO SCOoffice Server does not properly restrict I/O buffering, which allows...

The STARTTLS implementation in SCO SCOoffice Server does not properly restrict I/O buffering, which allows man-in-the-middle attackers to insert commands into encrypted SMTP sessions by sending a cleartext command that is processed after TLS is in place, related to a "plaintext command injection" attack, a similar issue to CVE-2011-0411.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE describes a flaw in SCO SCOoffice Server’s SMTP STARTTLS handling. A network attacker positioned between client and server could cause a cleartext SMTP command to be processed after encryption begins, undermining session integrity. The source bundle does not provide a CVSS score, affected versions, active exploitation evidence, or a named patch. Exposure is most likely limited to organizations still running SCO SCOoffice Server with SMTP STARTTLS reachable by users or mail relays. Internet-facing SMTP, shared networks, or untrusted network paths increase concern. The provided affected-product data is incomplete and lists no normalized versions or CPEs. Treat as a legacy mail-platform risk. Prioritize only if SCO SCOoffice Server is still present, especially on exposed SMTP paths. If not present, record as not applicable. If present and unsupported, plan replacement or isolation rather than relying on incomplete historical patch information. Mitigation focus: Inventory any SCO SCOoffice Server deployments and exposed SMTP services.; Check SCO or surviving vendor guidance for supported fixes or retirement advice.; Upgrade, replace, or isolate unsupported SCOoffice mail infrastructure..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2011-1432 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.