Bug 1462216 - (CVE-2017-7376) CVE-2017-7376 libxml2: Incorrect limit used for port values
CVE-2017-7376 libxml2: Incorrect limit used for port values
Status: CLOSED NOTABUG
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=20170417,reported=2...
: Security
Depends On: 1462226 1462227 1525811 1462228
Blocks: 1462234
  Show dependency treegraph
 
Reported: 2017-06-16 08:36 EDT by Adam Mariš
Modified: 2018-07-11 08:59 EDT (History)
33 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-30 01:21:35 EDT
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 Adam Mariš 2017-06-16 08:36:58 EDT
When calculating port value in xmlParse3986Port function, incorrect limit is used.

Android patch:

https://android.googlesource.com/platform/external/libxml2/+/51e0cb2e5ec18eaf6fb331bc573ff27b743898f4

References:

https://source.android.com/security/bulletin/2017-06-01#libraries
Comment 1 Adam Mariš 2017-06-16 08:49:03 EDT
Created libxml2 tracking bugs for this issue:

Affects: fedora-all [bug 1462226]


Created mingw-libxml2 tracking bugs for this issue:

Affects: epel-7 [bug 1462227]
Affects: fedora-all [bug 1462228]
Comment 3 Doran Moppert 2017-08-30 01:21:35 EDT
The port filtering functionality was introduced in 2.9.4

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