Issue metadata
Sign in to add a comment
|
CrOS: Vulnerability reported in net-misc/curl |
||||||||||||||||||||||
Issue descriptionAutomated analysis has detected that the following third party packages have had vulnerabilities publicly reported. NOTE: There may be several bugs listed below - in almost all cases, all bugs can be quickly addressed by upgrading to the latest version of the package. Package Name: net-misc/curl Package Version: [cpe:/a:curl:curl:7.51.0 cpe:/a:curl:libcurl:7.51.0 cpe:/a:haxx:curl:7.51.0 cpe:/a:haxx:libcurl:7.51.0] Advisory: CVE-2016-9952 Details: https://vomit.googleplex.com/advisory?id=CVE/CVE-2016-9952 CVSS severity score: 6.8/10.0 Confidence: high Description: The verify_certificate function in lib/vtls/schannel.c in libcurl 7.30.0 through 7.51.0, when built for Windows CE using the schannel TLS backend, makes it easier for remote attackers to conduct man-in-the-middle attacks via a crafted wildcard SAN in a server certificate, as demonstrated by "*.com." Advisory: CVE-2016-9953 Details: https://vomit.googleplex.com/advisory?id=CVE/CVE-2016-9953 CVSS severity score: 7.5/10.0 Confidence: high Description: The verify_certificate function in lib/vtls/schannel.c in libcurl 7.30.0 through 7.51.0, when built for Windows CE using the schannel TLS backend, allows remote attackers to obtain sensitive information, cause a denial of service (crash), or possibly have unspecified other impact via a wildcard certificate name, which triggers an out-of-bounds read.
,
Apr 11 2018
Assigned to severity low because CrOS should not be affected.
,
Apr 11 2018
Why is this tagged as kernel bug ? Please explain.
,
Apr 11 2018
Guenter - No good deed goes unpunished. :) My guess is it's directed to OS>Kernel mostly because our group handles most of the user space packages as well (update engine, metrics, recovery, etc). I've redirected to OS > Packages and cc'd the last three people to touch curl package. It seems to be as simple as bumping the curl version to a newer one.
,
Apr 11 2018
More importantly: why is a CVE from years ago just being reported against a version of curl that we are no longer shipping? I upgraded in bug 811049 .
,
Apr 11 2018
#5: Vomit re-evaluates CVEs if/when they are updated, and the CVEs were updated yesterday. Also, Vomit doesn't know anything about package versions used internally.
,
Apr 12 2018
,
Jul 19
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by xzhou@chromium.org
, Apr 11 2018