Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1601096 - (CVE-2018-1000613) CVE-2018-1000613 bouncycastle: lack of class checking in deserialization of XMSS/XMSS^MT private keys with BDS state information
CVE-2018-1000613 bouncycastle: lack of class checking in deserialization of X...
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20180303,repor...
: Security
Depends On: 1601099 1601098
Blocks: 1601100
  Show dependency treegraph
 
Reported: 2018-07-13 17:01 EDT by Laura Pardo
Modified: 2018-10-25 11:41 EDT (History)
51 users (show)

See Also:
Fixed In Version: bouncycastle 1.60
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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 Laura Pardo 2018-07-13 17:01:28 EDT
A flaw was found in Legion of the Bouncy Castle Java Cryptography APIs version prior to 1.60. A lack of class checking in the deserialization of XMSS/XMSS^MT private keys with BDS state information can result in the execution of unexpected code.


References:
https://github.com/bcgit/bc-java/commit/4092ede58da51af9a21e4825fbad0d9a3ef5a223#diff-2c06e2edef41db889ee14899e12bd574 	
https://github.com/bcgit/bc-java/commit/cd98322b171b15b3f88c5ec871175147893c31e6#diff-148a6c098af0199192d6aede960f45dc
Comment 1 Laura Pardo 2018-07-13 17:02:20 EDT
Created bouncycastle tracking bugs for this issue:

Affects: epel-all [bug 1601099]
Affects: fedora-all [bug 1601098]
Comment 2 Doran Moppert 2018-07-15 21:21:09 EDT
Statement:

The XMSS/XMSS^MT algorithms were first introduced in upstream bouncycastle version 1.57.  Versions prior to this, that have not had the new algorithms back-ported, are not affected.

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