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 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.

Weakness

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

Affected Software

Name	Vendor	Start Version	End Version
Openssl	Openssl	*	0.9.6i (excluding)
Openssl	Openssl	0.9.6i (including)	0.9.6i (including)
Openssl	Openssl	0.9.7 (including)	0.9.7 (including)
Openssl	Openssl	0.9.7-beta1 (including)	0.9.7-beta1 (including)
Openssl	Openssl	0.9.7-beta2 (including)	0.9.7-beta2 (including)
Openssl	Openssl	0.9.7-beta3 (including)	0.9.7-beta3 (including)
Openssl	Openssl	0.9.7-beta4 (including)	0.9.7-beta4 (including)
Openssl	Openssl	0.9.7-beta5 (including)	0.9.7-beta5 (including)
Openssl	Openssl	0.9.7-beta6 (including)	0.9.7-beta6 (including)
Red Hat Enterprise Linux AS (Advanced Server) version 2.1	RedHat		*
Red Hat Enterprise Linux ES version 2.1	RedHat		*
Red Hat Enterprise Linux WS version 2.1	RedHat		*
Red Hat Linux 6.2	RedHat		*
Red Hat Linux 7.0	RedHat		*
Red Hat Linux 7.1	RedHat		*
Red Hat Linux 7.1	RedHat		*
Red Hat Linux 7.2	RedHat		*
Red Hat Linux 7.3	RedHat		*
Red Hat Linux 8.0	RedHat		*
Red Hat Linux Advanced Workstation 2.1	RedHat		*
Red Hat Stronghold 3	RedHat		*
Red Hat Stronghold 4	RedHat		*
Openssl	Ubuntu	dapper	*
Openssl	Ubuntu	devel	*
Openssl	Ubuntu	edgy	*
Openssl	Ubuntu	feisty	*
Openssl097	Ubuntu	dapper	*
Openssl097	Ubuntu	devel	*
Openssl097	Ubuntu	edgy	*
Openssl097	Ubuntu	feisty	*

Potential Mitigations

Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.

https://cwe.mitre.org/data/definitions/189.html

NVD	https://nvd.nist.gov/vuln/detail/CVE-2003-0078
CWE	https://cwe.mitre.org/data/definitions/203.html

Observable Discrepancy

Weakness

Affected Software

Potential Mitigations

References

CVE-2003-0078

Observable Discrepancy

Weakness

Affected Software

Potential Mitigations

Related Attack Patterns

References