BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2023-6516High confidence

Specific recursive query patterns may lead to an out-of-memory condition

ISC · BIND 9

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
SSA-915275 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-915275: Multiple Vulnerabilities in SINEC INS Before V1.0 SP2 Update 3
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SINEC INS
Summary
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.
Remediation
Update to V1.0 SP2 Update 3 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-58747

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Memory Allocation with Excessive Size Value → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-789 ↗

CWE-789: Memory Allocation with Excessive Size Value. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-789
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-W-2024-1307Red Hat OpenShift Service Mesh Containers: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Service Mesh Containers ausnutzen, um Dateien zu manipulieren, einen 'Denial of Service'-Zustand erzuegen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen oder weitere nicht spezifizierte Angriffe durchzuführen.

Official advisory
BSI · German · WID-SEC-W-2024-1248Xerox FreeFlow Print Server: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden

Official advisory
BSI · German · WID-SEC-W-2024-0386Internet Systems Consortium BIND: Mehrere Schwachstellen ermöglichen Denial of Service

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Internet Systems Consortium BIND ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory
CERT-FR · French · CERTFR-2025-AVI-0018Multiples vulnérabilités dans les produits Juniper Networks

/CVERecord?id=CVE-2023-4408 Référence CVE CVE-2023-50387 https://www.cve.org/CVERecord?id=CVE-2023-50387 Référence CVE CVE-2023-50868 https://www.cve.org/CVERecord?id=CVE-2023-50868 Référence CVE CVE-2023-5088 https://www.cve.org/CVERecord?id=CVE-2023-5088 Référence CVE CVE-2023-52463 https://www.cve.org/CVERecord?id=CVE-2023-52463 Référence CVE CVE-2023-52801 https://www.cve.org/CVERecord?id=CVE-2023-52801 Référence CVE CVE-2023-5517 https://www.cve.org/CVERecord?id=CVE-2023-5517 Référence CVE CVE-2023-5679 https://www.cve.org/CVERecord?id=CVE-2023-5679 Référence CVE CVE-2023-6240 https://www.cve.org/CVERecord?id=CVE-2023-6240 Référence CVE CVE-2023-6516 https://www.cve.org/CVERecord?id=CVE-2023-6516 Référence CVE CVE-2023-6683 https://www.cve.org/CVERecord?id=CVE-2023-6683 Référence CVE CVE-2023-7008 https://www.cve.org/CVERecord?id=CVE-2023-7008 Référence CVE CVE-2024-1488 https://www.cve.org/CVERecord?id=CVE-2024-1488 Référence CVE CVE-2024-25742 https://www.cve.org/CVERecord?id=CVE-2024-25742 Référence CVE CVE-2024-25743 https://www.cve.org/CVERecord?id=CVE-2024-25743 Référence CVE CVE-2024-26629 https://www.cve.org/CVERecord?id=CVE-2024-26629 Référence CVE CVE-2024-26630 https://www.cve.org/CVERecord?id=CVE-2024-26630 Référence CVE CVE-2024-26720 https://www.cve.org/CVERecord?id=CVE-202

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0470Multiples vulnérabilités dans les produits IBM

g/CVERecord?id=CVE-2023-40550 Référence CVE CVE-2023-40551 https://www.cve.org/CVERecord?id=CVE-2023-40551 Référence CVE CVE-2023-4408 https://www.cve.org/CVERecord?id=CVE-2023-4408 Référence CVE CVE-2023-50387 https://www.cve.org/CVERecord?id=CVE-2023-50387 Référence CVE CVE-2023-50868 https://www.cve.org/CVERecord?id=CVE-2023-50868 Référence CVE CVE-2023-5517 https://www.cve.org/CVERecord?id=CVE-2023-5517 Référence CVE CVE-2023-5679 https://www.cve.org/CVERecord?id=CVE-2023-5679 Référence CVE CVE-2023-6129 https://www.cve.org/CVERecord?id=CVE-2023-6129 Référence CVE CVE-2023-6237 https://www.cve.org/CVERecord?id=CVE-2023-6237 Référence CVE CVE-2023-6516 https://www.cve.org/CVERecord?id=CVE-2023-6516 Référence CVE CVE-2024-0727 https://www.cve.org/CVERecord?id=CVE-2024-0727 Référence CVE CVE-2024-20918 https://www.cve.org/CVERecord?id=CVE-2024-20918 Référence CVE CVE-2024-20919 https://www.cve.org/CVERecord?id=CVE-2024-20919 Référence CVE CVE-2024-20921 https://www.cve.org/CVERecord?id=CVE-2024-20921 Référence CVE CVE-2024-20926 https://www.cve.org/CVERecord?id=CVE-2024-20926 Référence CVE CVE-2024-20945 https://www.cve.org/CVERecord?id=CVE-2024-20945 Référence CVE CVE-2024-20952 https://www.cve.org/CVERecord?id=CVE-2024-20952 Référence CVE CVE-2024-21011 https://www.cve.org/CVERecord?id=CVE

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0122Multiples vulnérabilités dans Bind

De multiples vulnérabilités ont été découvertes dans Bind . Elles permettent à un attaquant de provoquer un déni de service à distance.

Official advisory
NCSC-NL · Dutch · NCSC-2024-0433Kwetsbaarheden verholpen in Siemens producten

De kwetsbaarheden stellen een kwaadwillende mogelijk in staat aanvallen uit te voeren die kunnen leiden tot de volgende categorieën schade: - Denial-of-Service (DoS) - Cross-Site-Scripting (XSS) - Manipulatie van gegevens - Omzeilen van een beveiligingsmaatregel - Omzeilen van authenticatie - (Remote) code execution (Administrator/Root rechten) - (Remote) code execution (Gebruikersrechten) - Toegang tot systeemgegevens - Verhoogde gebruikersrechten De kwaadwillende heeft hiervoor toegang nodig tot de productieomgeving. Het is goed gebruik een dergelijke omgeving niet publiek toegankelijk te hebben.

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
SINEC INS
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Update to V1.0 SP2 Update 3 or later version
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 13 Feb 2024 · Last source change 13 Feb 2025, 17:26 UTC · CWE-789 · Memory Allocation with Excessive Size Value

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-58747
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2023-58747↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-6516 · cve.blacktree.nl