Is PAM 3.1.1 affected by CVE-2019-1559?
search cancel

Is PAM 3.1.1 affected by CVE-2019-1559?


Article ID: 129465


Updated On:


CA Privileged Access Manager - Cloakware Password Authority (PA) CA Privileged Access Manager (PAM)


We need to know if this finding is applicable to CA PAM 3.1.x if so what is the proposed mitigation.
STIG Finding Severity: Category I
CVEs: CVE-2019-1559
CVE-2019-1559: 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).


Component: CAPAMX


PAM 3.1.1 uses OpenSSL 1.0.2k, which is vulnerable to this attack.
PAM 3.3 updated the OpenSSL and uses OpenSSL 1.0.2r, which is not.
However, if you are using FIPS mode, then you are not using OpenSSL, but Wolf SSL, which is not reported to be vulnerable to this attack in this CVE.