CVE-2017-31457.5HighCWE-416

CVE-2017-3145: Improper fetch cleanup sequencing in the resolver can cause named to crash

ISC · BIND 9

Vendor fix available · Affected: ISC BIND 9 · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

27.7%probability of exploitation in the next 30 days

98th percentile

050100

Higher than 98% of scored CVEs

7.5HighCVSS 3.0

LowMediumHighCrit.

DescriptionCVE.org

BIND was improperly sequencing cleanup operations on upstream recursion fetch contexts, leading in some cases to a use-after-free error that can trigger an assertion failure and crash in named. Affects BIND 9.0.0 to 9.8.x, 9.9.0 to 9.9.11, 9.10.0 to 9.10.6, 9.11.0 to 9.11.2, 9.9.3-S1 to 9.9.11-S1, 9.10.5-S1 to 9.10.6-S1, 9.12.0a1 to 9.12.0rc1.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

ISC · BIND 99.0.0 to 9.8.x, 9.9.0 to 9.9.11, 9.10.0 to 9.10.6, 9.11.0 t…

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use After Free · Memory Corruption
Vendor: ISC
Published: January 2019
Band: Likely to be exploited (10% or more), January 2019

CoverageNo articles yet

No CyberSIXT article names CVE-2017-3145 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.