Bug 23859 - qpid-proton-java new security issues CVE-2018-17187 and CVE-2019-0223
Summary: qpid-proton-java new security issues CVE-2018-17187 and CVE-2019-0223
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Java Stack Maintainers
QA Contact: Sec team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-19 04:45 CET by David Walser
Modified: 2021-07-01 18:17 CEST (History)
1 user (show)

See Also:
Source RPM: qpid-proton-java-0.12.2-2.mga7.src.rpm
CVE:
Status comment: Fixed upstream in 0.30.0

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2018-11-19 04:45:53 CET 
Apache has issued an advisory on November 12:
https://www.openwall.com/lists/oss-security/2018/11/12/2

The issue is fixed upstream in 0.30.0.

Mageia 6 is also affected.
David Walser 2018-11-19 04:46:01 CET

Whiteboard: (none) => MGA6TOO

David Walser 2019-02-03 02:45:56 CET

Status comment: (none) => Fixed upstream in 0.30.0

Comment 1 David Walser 2019-04-23 14:04:17 CEST 
Apache has issued an advisory today (April 23):
https://www.openwall.com/lists/oss-security/2019/04/23/4

The issue is fixed upstream in 0.27.1.

Mageia 6 is also affected.

Summary: qpid-proton-java new security issue CVE-2018-17187 => qpid-proton-java new security issues CVE-2018-17187 and CVE-2019-0223
Severity: normal => major

David Walser 2019-06-23 19:31:43 CEST

Whiteboard: MGA6TOO => MGA7TOO, MGA6TOO

Nicolas Lécureuil 2020-05-22 14:08:20 CEST

CC: (none) => mageia
Whiteboard: MGA7TOO, MGA6TOO => MGA7TOO

Comment 2 Nicolas Lécureuil 2020-12-26 23:31:28 CET 
Not in cauldron anymore

Version: Cauldron => 7
Whiteboard: MGA7TOO => (none)

Comment 3 David Walser 2021-07-01 18:17:49 CEST 
https://blog.mageia.org/en/2021/06/08/mageia-7-will-reach-end-of-support-on-30th-of-june-the-king-is-dead-long-live-the-king/

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.