CVE-2019-1559

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>linux-c7-openssl-devel</name>
	<range><lt>1.0.2r</lt></range>
      </package>
      <package>
	<name>openssl-unsafe</name>
	<range><lt>1.0.2r</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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).</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2019-1559</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2019-1559</url>
    </references>
    <dates>
      <discovery>2019-02-27</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>