CVE-2003-0078: n/a vulnerability

CVE-2003-0078: ssl3_get_record in s3_pkt.c for OpenSSL before 0.9.7a and 0.9.6 before 0.9.6i does not perform a MAC comput...

ssl3_get_record in s3_pkt.c for OpenSSL before 0.9.7a and 0.9.6 before 0.9.6i does not perform a MAC computation if an incorrect block cipher padding is used, which causes an information leak (timing discrepancy) that may make it easier to launch cryptographic attacks that rely on distinguishing between padding and MAC verification errors, possibly leading to extraction of the original plaintext, aka the "Vaudenay timing attack."

UnknownCVSS not scoredNot KEV-listedUpdatedAug 8, 2024, 01:43 UTC (UTC+00:00)

Security readout for executives and security teams

This is an old OpenSSL flaw where certain SSL/TLS errors could respond at measurably different speeds. That timing leak may help an attacker weaken encrypted sessions and potentially recover plaintext in some conditions. Business urgency is mainly for legacy systems still running OpenSSL before 0.9.7a or 0.9.6i. Exposure is most likely in obsolete servers, appliances, embedded systems, or legacy distributions still using OpenSSL before 0.9.7a, or the 0.9.6 branch before 0.9.6i. Modern supported platforms are unlikely to be affected unless they carry very old bundled OpenSSL code. Treat this as a legacy exposure cleanup item, not a current mass-exploitation emergency based on the supplied evidence. If affected OpenSSL versions remain on exposed or regulated systems, prioritize remediation because the weakness affects encryption confidentiality. Mitigation focus: Upgrade OpenSSL to 0.9.7a, 0.9.6i, or later vendor-fixed packages.; Prioritize externally reachable SSL/TLS services and security-sensitive legacy systems.; Check operating system vendor advisories for fixed package names and backported patches..

Prepared: Jun 30, 2026, 03:02 UTC (UTC+00:00)

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.

cve · low confidence lookup

CVE-2003-0078 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: Sep 1, 2004, 04:00 UTC (UTC+00:00)

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

1Source links

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

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.