Improperly Implemented Security Check for Standard Affecting unbound-python package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL7-UNBOUNDPYTHON-1366134
- published26 Jul 2021
- disclosed19 Jan 2018
Introduced: 19 Jan 2018
CVE-2017-15105 (opens in a new tab)How to fix?
There is no fixed version for RHEL:7 unbound-python.
NVD Description
Note: Versions mentioned in the description apply only to the upstream unbound-python package and not the unbound-python package as distributed by RHEL.
See How to fix? for RHEL:7 relevant fixed versions and status.
A flaw was found in the way unbound before 1.6.8 validated wildcard-synthesized NSEC records. An improperly validated wildcard NSEC record could be used to prove the non-existence (NXDOMAIN answer) of an existing wildcard record, or trick unbound into accepting a NODATA proof.
References
- http://www.securityfocus.com/bid/102817
- https://unbound.net/downloads/CVE-2017-15105.txt
- https://access.redhat.com/security/cve/CVE-2017-15105
- https://lists.debian.org/debian-lts-announce/2018/01/msg00039.html
- https://lists.debian.org/debian-lts-announce/2019/02/msg00022.html
- https://usn.ubuntu.com/3673-1/