Bug 1869639 (CVE-2020-26154) - CVE-2020-26154 libproxy: sending more than 102400 bytes in PAC without a Content-Length present could result in buffer overflow
Summary: CVE-2020-26154 libproxy: sending more than 102400 bytes in PAC without a Cont...
Keywords:
Status: NEW
Alias: CVE-2020-26154
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: 1883584 1884639
Blocks: 1869641
TreeView+ depends on / blocked
 
Reported: 2020-08-18 12:20 UTC by Michael Kaplan
Modified: 2024-03-27 16:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description Michael Kaplan 2020-08-18 12:20:23 UTC 
It was found that if the server serving a PAC file sends more than 102400 bytes without a Content-Length present, libproxy can overflow its buffer by PAC_HTTP_BLOCK_SIZE (512) bytes.

References:

https://github.com/libproxy/libproxy/pull/126
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968366
Comment 2 Stefan Cornelius 2020-09-29 15:55:02 UTC 
Created libproxy tracking bugs for this issue:

Affects: fedora-all [bug 1883584]
Comment 7 Nick Boldt 2022-07-21 19:03:45 UTC 
Is this issue ever going to be fixed in RHEL8 ?

Asking because I got asked to fix this in our RHEL8 based containers back on 2020/10/13 in https://issues.redhat.com/browse/CRW-1290 but as of UBI 8.6 the latest RPM is still 

libproxy-0.4.15-5.2.el8

But according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968366 we need 0.4.15-15

Since we depend on RHEL8 / UBI8 containers for our image builds, this isn't something we can fix downstream... instead it needs a RHEL RPM fix, which we can then inherit.
Note You need to log in before you can comment on or make changes to this bug.