Important: bind security update

bind Updated 02 Oct 2025

Summary

04/10/2022

Disclosed on

N/A

Severity

Yes i

Fix available

Unrated

Severity

Not published

CVSS Score

ALSA-2022:6778: Important: bind security update. Affects bind versions < 32:9.11.36-3.el8_6.1. Fixed in 32:9.11.36-3.el8_6.1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.

Vulnerability Detail

A memory leak vulnerability has been discovered in the ECDSA and EdDSA DNSSEC verification code of BIND. This vulnerability could be exploited by an attacker to cause a denial of service (DoS) condition by exhausting system memory.

How To Fix

Minimum fixed version

32:9.11.36-3.el8_6.1

This is the first release that contains the fix.

sudo dnf update bind

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the security update as soon as possible.

Conclusion

It is important to update the affected BIND package to address the memory leak vulnerabilities in the ECDSA and EdDSA DNSSEC verification code. Failure to do so could leave your system vulnerable to denial of service attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for bind →

FAQ

What is BIND?

BIND is an implementation of the Domain Name System (DNS) protocols.

What is DNSSEC?

DNSSEC is a set of extensions to DNS that provide authentication and integrity checking of DNS data.

What is a memory leak?

A memory leak is a type of software bug where a program fails to release memory that it no longer needs, resulting in a gradual loss of available memory.

What is the impact of this vulnerability?

This vulnerability could be exploited by an attacker to cause a denial of service (DoS) condition by exhausting system memory.

How can I check if my system is affected?

You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) to the playground and it will alert you if any open-source vulnerabilities are found.

References

Related vulnerabilities

Recent vulnerabilities recorded for bind.

View all bind vulnerabilities →

How To Fix

Minimum fixed version

32:9.11.36-3.el8_6.1

This is the first release that contains the fix.

sudo dnf update bind

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram

Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.

Join the channel →