| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ISC BIND up to 9.16.41/9.16.41-S1/9.18.15/9.18.15-S1/9.19.13 and classified as critical. This issue affects some unknown processing of the component Cache Handler. Such manipulation leads to resource consumption. This vulnerability is uniquely identified as CVE-2023-2828. The attack can be launched remotely. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in ISC BIND up to 9.16.41/9.16.41-S1/9.18.15/9.18.15-S1/9.19.13 (Domain Name Software). It has been rated as critical. Affected by this issue is an unknown code of the component Cache Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. CVE summarizes:
Every `named` instance configured to run as a recursive resolver maintains a cache database holding the responses to the queries it has recently sent to authoritative servers. The size limit for that cache database can be configured using the `max-cache-size` statement in the configuration file; it defaults to 90% of the total amount of memory available on the host. When the size of the cache reaches 7/8 of the configured limit, a cache-cleaning algorithm starts to remove expired and/or least-recently used RRsets from the cache, to keep memory use below the configured limit. It has been discovered that the effectiveness of the cache-cleaning algorithm used in `named` can be severely diminished by querying the resolver for specific RRsets in a certain order, effectively allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.11.0 through 9.16.41, 9.18.0 through 9.18.15, 9.19.0 through 9.19.13, 9.11.3-S1 through 9.16.41-S1, and 9.18.11-S1 through 9.18.15-S1.
The weakness was disclosed 06/22/2023. The advisory is available at kb.isc.org. This vulnerability is handled as CVE-2023-2828 since 05/22/2023. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
The vulnerability scanner Nessus provides a plugin with the ID 240012 (TencentOS Server 3: bind9.16 (TSSA-2023:0198)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 9.16.42, 9.16.42-S1, 9.18.16, 9.18.16-S1 or 9.19.14 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (240012). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 9.16.0
- 9.16.1
- 9.16.2
- 9.16.3
- 9.16.4
- 9.16.5
- 9.16.6
- 9.16.7
- 9.16.8
- 9.16.9
- 9.16.10
- 9.16.11
- 9.16.12
- 9.16.13
- 9.16.14
- 9.16.15
- 9.16.16
- 9.16.17
- 9.16.18
- 9.16.19
- 9.16.20
- 9.16.21
- 9.16.22
- 9.16.23
- 9.16.24
- 9.16.25
- 9.16.26
- 9.16.27
- 9.16.28
- 9.16.29
- 9.16.30
- 9.16.31
- 9.16.32
- 9.16.33
- 9.16.34
- 9.16.35
- 9.16.36
- 9.16.37
- 9.16.38
- 9.16.39
- 9.16.40
- 9.16.41
- 9.16.41-S1
- 9.18.0
- 9.18.1
- 9.18.2
- 9.18.3
- 9.18.4
- 9.18.5
- 9.18.6
- 9.18.7
- 9.18.8
- 9.18.9
- 9.18.10
- 9.18.11
- 9.18.12
- 9.18.13
- 9.18.14
- 9.18.15
- 9.18.15-S1
- 9.19.0
- 9.19.1
- 9.19.2
- 9.19.3
- 9.19.4
- 9.19.5
- 9.19.6
- 9.19.7
- 9.19.8
- 9.19.9
- 9.19.10
- 9.19.11
- 9.19.12
- 9.19.13
License
Website
- Vendor: https://www.isc.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (Internet Systems Consortium (ISC)): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 240012
Nessus Name: TencentOS Server 3: bind9.16 (TSSA-2023:0198)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: BIND 9.16.42/9.16.42-S1/9.18.16/9.18.16-S1/9.19.14
Timeline
05/22/2023 🔍06/22/2023 🔍
06/22/2023 🔍
06/17/2025 🔍
Sources
Vendor: isc.orgAdvisory: FEDORA-2023-1d526d551c
Status: Confirmed
CVE: CVE-2023-2828 (🔍)
GCVE (CVE): GCVE-0-2023-2828
GCVE (VulDB): GCVE-100-232082
Entry
Created: 06/22/2023 06:09Updated: 06/17/2025 15:45
Changes: 06/22/2023 06:09 (51), 07/16/2023 14:50 (1), 06/17/2025 15:45 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.