Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 99.99% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2024
CVE-2023-50387High confidence
n/a — Allocation of Resources Without Limits or Throttling
Unknown · Unknown
Official source article: Siemens SSA-915275 ↗. Check the applicable product and release in the original source.
7.5HighCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 5 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Siemens ProductCERT: 1 affected or under-investigation product state without a fixed product state in the same current advisory
- Debian Security Tracker: 1 affected package state with no published fix
Distribution package intelligence
45 package statesRelease-specific package status
Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | knot-resolver | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.7.1-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | pdns-recursor | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.0.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · main | bind | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 9.18.24-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.23v3.23 · main | dnsmasq | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.90-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.23v3.23 · main | unbound | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.19.1-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · community | knot-resolver | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.7.1-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | pdns-recursor | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.0.2-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · main | bind | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 9.18.24-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | dnsmasq | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.90-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.22v3.22 · main | unbound | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.19.1-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · community | knot-resolver | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.7.1-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · community | pdns-recursor | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 5.0.2-r0 | Alpine Security Database ↗Source updated 19 Aug 2026 |
| Alpine v3.21v3.21 · main | bind | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 9.18.24-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | dnsmasq | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 2.90-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Alpine v3.21v3.21 · main | unbound | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 1.19.1-r0 | Alpine Security Database ↗Source updated 3 Oct 2026 |
| Debian trixietrixie · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.19.21-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | dnsjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.6.2-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.90-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | knot-resolver | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.7.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | pdns-recursor | Vendor fix publishedDebian records a fixed source-package version for this release. | 4.9.3-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | systemd | Vendor fix publishedDebian records a fixed source-package version for this release. | 255.4-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | unbound | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.19.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.18.24-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | dnsjava | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.90-4~deb12u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | knot-resolver | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.6.0-1+deb12u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | pdns-recursor | Vendor fix publishedDebian records a fixed source-package version for this release. | 4.8.6-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | systemd | Vendor fix publishedDebian records a fixed source-package version for this release. | 252.23-1~deb12u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | unbound | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.17.1-2+deb12u2 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.19.21-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | dnsjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.6.2-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.90-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | knot-resolver | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.7.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | pdns-recursor | Vendor fix publishedDebian records a fixed source-package version for this release. | 4.9.3-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | systemd | Vendor fix publishedDebian records a fixed source-package version for this release. | 255.4-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | unbound | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.19.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | bind9 | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:9.19.21-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | dnsjava | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.6.2-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | dnsmasq | Vendor fix publishedDebian records a fixed source-package version for this release. | 2.90-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | knot-resolver | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.7.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | pdns-recursor | Vendor fix publishedDebian records a fixed source-package version for this release. | 4.9.3-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | systemd | Vendor fix publishedDebian records a fixed source-package version for this release. | 255.4-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | unbound | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.19.1-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | isc-dhcp | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | unbound | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 1.19.1-1ubuntu1 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative 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.
SSA-915275 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-915275: Multiple Vulnerabilities in SINEC INS Before V1.0 SP2 Update 3
The vendor explicitly identifies these products as affected by this CVE.
- SINEC INS
- Summary
- Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
- Remediation
- Update to V1.0 SP2 Update 3 or later version
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
What
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
Why
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
What
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
Why
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.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 → Allocation of Resources Without Limits or Throttling → disrupt the affected service
- 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-770 ↗
CWE-770: Allocation of Resources Without Limits or Throttling. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can 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:HCommon 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.
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. - Fix availability varies by product
- Affected
- SINEC INS
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- 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 14 Feb 2024 · Last source change 4 Nov 2025, 18:20 UTC · CWE-770 · Allocation of Resources Without Limits or Throttling
CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2023-55182
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCISA ADP
NVD statusNVD modified after enrichment
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
CVE published
Fixed release or patch reference recorded
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.