ISC BIND up to 9.16.45/9.16.45-S1 named allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in ISC BIND up to 9.16.45/9.16.45-S1. This affects an unknown part of the component named. Performing a manipulation results in allocation of resources. This vulnerability was named CVE-2023-6516. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability was found in ISC BIND up to 9.16.45/9.16.45-S1 (Domain Name Software). It has been classified as critical. This affects some unknown functionality of the component named. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:
To keep its cache database efficient, `named` running as a recursive resolver occasionally attempts to clean up the database. It uses several methods, including some that are asynchronous: a small chunk of memory pointing to the cache element that can be cleaned up is first allocated and then queued for later processing. It was discovered that if the resolver is continuously processing query patterns triggering this type of cache-database maintenance, `named` may not be able to handle the cleanup events in a timely manner. This in turn enables the list of queued cleanup events to grow infinitely large over time, allowing the configured `max-cache-size` limit to be significantly exceeded. This issue affects BIND 9 versions 9.16.0 through 9.16.45 and 9.16.8-S1 through 9.16.45-S1.
The weakness was presented 02/13/2024. It is possible to read the advisory at kb.isc.org. This vulnerability is uniquely identified as CVE-2023-6516 since 12/05/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 9.16.48 or 9.16.48-S1 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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.42
- 9.16.43
- 9.16.44
- 9.16.45
- 9.16.45-S1
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: Allocation of resourcesCWE: CWE-770 / 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: BIND 9.16.48/9.16.48-S1
Timeline
12/05/2023 🔍02/13/2024 🔍
02/13/2024 🔍
03/04/2024 🔍
Sources
Vendor: isc.orgAdvisory: FEDORA-2024-21310568fa
Status: Confirmed
CVE: CVE-2023-6516 (🔍)
GCVE (CVE): GCVE-0-2023-6516
GCVE (VulDB): GCVE-100-253563
Entry
Created: 02/13/2024 15:17Updated: 03/04/2024 08:09
Changes: 02/13/2024 15:17 (50), 03/04/2024 08:08 (1), 03/04/2024 08:09 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.