Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1330179 - (CVE-2016-3702) CVE-2016-3702 CFME vulnerable to padding oracle attack against AES-256-CBC
CVE-2016-3702 CFME vulnerable to padding oracle attack against AES-256-CBC
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20160425,reported=2...
: Security
Depends On: 1366330
Blocks: 1330182
  Show dependency treegraph
 
Reported: 2016-04-25 10:29 EDT by Ján Rusnačko
Modified: 2016-12-19 22:54 EST (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A padding oracle flaw was found in the encryption of sensitive information stored within the backend database used by CloudForms. An attacker able to submit forged cipher texts could observe the results of encryption and determine information that could, in turn, lead to the disclosure of encrypted data within the database.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-12-19 22:54:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ján Rusnačko 2016-04-25 10:29:51 EDT
Internally CFME uses AES-256-CBC encryption to encrypt important data before it is saved in the database. This encryption mode is vulnerable to padding oracle attack and CFME does allow attacker to submit forged ciphertexts for encryption and observe the result.
Comment 1 Ján Rusnačko 2016-04-25 10:30:05 EDT
Acknowledgments:

Name: Travis Scheponik (Red Hat)
Comment 6 Kurt Seifried 2016-12-19 22:54:30 EST
Statement: 

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.