Bug 2169845 (CVE-2023-0833) - CVE-2023-0833 Red Hat A-MQ Streams: component version with information disclosure flaw
Summary: CVE-2023-0833 Red Hat A-MQ Streams: component version with information disclo...
Keywords:
Status: NEW
Alias: CVE-2023-0833
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2169842
TreeView+ depends on / blocked
 
Reported: 2023-02-14 18:58 UTC by Chess Hazlett
Modified: 2023-09-25 19:52 UTC (History)
4 users (show)

Fixed In Version: okhttp 4.9.2
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in Red Hat's AMQ-Streams, which ships a version of the OKHttp component with an information disclosure flaw via an exception triggered by a header containing an illegal value. This issue could allow an authenticated attacker to access information outside of their regular permissions.
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:1241 0 None None None 2023-03-14 18:47:53 UTC
Red Hat Product Errata RHSA-2023:3223 0 None None None 2023-05-18 09:54:37 UTC

Description Chess Hazlett 2023-02-14 18:58:11 UTC
It was found that Red Hat's AMQ-Streams ships a version of OKHttp component with an information disclosure flaw via an exception triggered by a header containing an illegal value. An authenticated attacker could possibly use this flaw to access information outside of their regular permissions.

Comment 3 errata-xmlrpc 2023-03-14 18:47:52 UTC
This issue has been addressed in the following products:

  Red Hat AMQ Streams 2.2.1

Via RHSA-2023:1241 https://access.redhat.com/errata/RHSA-2023:1241

Comment 5 errata-xmlrpc 2023-05-18 09:54:36 UTC
This issue has been addressed in the following products:

  Red Hat AMQ Streams 2.4.0

Via RHSA-2023:3223 https://access.redhat.com/errata/RHSA-2023:3223


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