Description
If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).
Remediation
References
Related Vulnerabilities
WordPress 6.1.x Multiple Vulnerabilities (6.1 - 6.1.6)
WordPress Plugin Music Store Cross-Site Scripting (1.0.41)
Joomla Cryptographic Issues Vulnerability (CVE-2008-4122)
WordPress 5.2.x Multiple Vulnerabilities (5.2 - 5.2.3)
JBoss Application Server Privilege Escalation Vulnerability (CVE-2007-1354)