{"url":"http://public2.vulnerablecode.io/api/packages/469217?format=json","purl":"pkg:apk/alpine/curl@7.53.0-r0?arch=s390x&distroversion=v3.18&reponame=main","type":"apk","namespace":"alpine","name":"curl","version":"7.53.0-r0","qualifiers":{"arch":"s390x","distroversion":"v3.18","reponame":"main"},"subpath":"","is_vulnerable":false,"next_non_vulnerable_version":"7.53.1-r2","latest_non_vulnerable_version":"8.12.0-r0","affected_by_vulnerabilities":[],"fixing_vulnerabilities":[{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/65676?format=json","vulnerability_id":"VCID-w63e-dku9-mqe9","summary":"curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server's certificate's validity in the code that checks for a test success or failure. It ends up always thinking there's valid proof, even when there is none or if the server doesn't support the TLS extension in question. This could lead to users not detecting when a server's certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).","references":[{"reference_url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2017-2629.json","reference_id":"","reference_type":"","scores":[{"value":"4.3","scoring_system":"cvssv3","scoring_elements":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N"}],"url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2017-2629.json"},{"reference_url":"https://api.first.org/data/v1/epss?cve=CVE-2017-2629","reference_id":"","reference_type":"","scores":[{"value":"0.00365","scoring_system":"epss","scoring_elements":"0.58827","published_at":"2026-06-09T12:55:00Z"},{"value":"0.00365","scoring_system":"epss","scoring_elements":"0.58781","published_at":"2026-06-04T12:55:00Z"},{"value":"0.00365","scoring_system":"epss","scoring_elements":"0.58826","published_at":"2026-06-07T12:55:00Z"},{"value":"0.00365","scoring_system":"epss","scoring_elements":"0.58834","published_at":"2026-06-06T12:55:00Z"},{"value":"0.00365","scoring_system":"epss","scoring_elements":"0.58828","published_at":"2026-06-05T12:55:00Z"},{"value":"0.00365","scoring_system":"epss","scoring_elements":"0.58811","published_at":"2026-06-08T12:55:00Z"}],"url":"https://api.first.org/data/v1/epss?cve=CVE-2017-2629"},{"reference_url":"https://curl.se/docs/CVE-2017-2629.html","reference_id":"","reference_type":"","scores":[{"value":"Medium","scoring_system":"cvssv3.1","scoring_elements":""}],"url":"https://curl.se/docs/CVE-2017-2629.html"},{"reference_url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2629","reference_id":"","reference_type":"","scores":[],"url":"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2629"},{"reference_url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml","reference_id":"","reference_type":"","scores":[{"value":"5.8","scoring_system":"cvssv2","scoring_elements":"AV:N/AC:M/Au:N/C:P/I:P/A:N"}],"url":"https://ftp.suse.com/pub/projects/security/yaml/suse-cvss-scores.yaml"},{"reference_url":"https://bugzilla.redhat.com/show_bug.cgi?id=1425746","reference_id":"1425746","reference_type":"","scores":[],"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1425746"},{"reference_url":"https://security.archlinux.org/ASA-201703-1","reference_id":"ASA-201703-1","reference_type":"","scores":[],"url":"https://security.archlinux.org/ASA-201703-1"},{"reference_url":"https://security.archlinux.org/AVG-179","reference_id":"AVG-179","reference_type":"","scores":[{"value":"Low","scoring_system":"archlinux","scoring_elements":""}],"url":"https://security.archlinux.org/AVG-179"},{"reference_url":"https://security.archlinux.org/AVG-180","reference_id":"AVG-180","reference_type":"","scores":[{"value":"Medium","scoring_system":"archlinux","scoring_elements":""}],"url":"https://security.archlinux.org/AVG-180"},{"reference_url":"https://security.archlinux.org/AVG-181","reference_id":"AVG-181","reference_type":"","scores":[{"value":"Medium","scoring_system":"archlinux","scoring_elements":""}],"url":"https://security.archlinux.org/AVG-181"},{"reference_url":"https://security.archlinux.org/AVG-182","reference_id":"AVG-182","reference_type":"","scores":[{"value":"Low","scoring_system":"archlinux","scoring_elements":""}],"url":"https://security.archlinux.org/AVG-182"},{"reference_url":"https://security.archlinux.org/AVG-183","reference_id":"AVG-183","reference_type":"","scores":[{"value":"Medium","scoring_system":"archlinux","scoring_elements":""}],"url":"https://security.archlinux.org/AVG-183"},{"reference_url":"https://security.archlinux.org/AVG-184","reference_id":"AVG-184","reference_type":"","scores":[{"value":"Medium","scoring_system":"archlinux","scoring_elements":""}],"url":"https://security.archlinux.org/AVG-184"},{"reference_url":"https://security.gentoo.org/glsa/201703-04","reference_id":"GLSA-201703-04","reference_type":"","scores":[],"url":"https://security.gentoo.org/glsa/201703-04"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/469217?format=json","purl":"pkg:apk/alpine/curl@7.53.0-r0?arch=s390x&distroversion=v3.18&reponame=main","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/curl@7.53.0-r0%3Farch=s390x&distroversion=v3.18&reponame=main"}],"aliases":["CVE-2017-2629"],"risk_score":3.1,"exploitability":"0.5","weighted_severity":"6.2","resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-w63e-dku9-mqe9"}],"risk_score":null,"resource_url":"http://public2.vulnerablecode.io/packages/pkg:apk/alpine/curl@7.53.0-r0%3Farch=s390x&distroversion=v3.18&reponame=main"}