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

A stack exhaustion flaw in control channel code may cause named to terminate unexpectedly

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
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivebind9Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1:9.18.18-0ubuntu2Canonical record ↗Source updated 4 Sept 2026
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.

2 current
2NGA002579 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)ABB Arctic communication solution ARM600 Vulnerabilities
2 known affected

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

  • ABB M2M Gateway ARM600, firmware versions >=4.1.2|<=5.0.3
  • ABB M2M Gateway SW, software versions >=5.0.1|<=5.0.3
Summary
The vulnerability involves the recursive processing of control channel messages sent to named, which can exhaust stack memory and cause named to terminate unexpectedly. Exploiting this flaw requires only network access to the control channel's configured TCP port, without needing a valid RNDC key.
Remediation
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 3. ARM600 system is by default not dependent on the name service (DNS). If name service is not used in the system, the name service port (TCP/UDP port 53) can be blocked by a firewall. Refer to section General security recommendations for additional advice on how to keep your system secure.
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
The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-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-44009

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

The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.

What

The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.

Why

The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.

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

The code that processes control channel messages sent to `named` calls certain functions recursively during packet parsing. Recursion depth is only limited by the maximum accepted packet size; depending on the environment, this may cause the packet-parsing code to run out of available stack memory, causing `named` to terminate unexpectedly. Since each incoming control channel message is fully parsed before its contents are authenticated, exploiting this flaw does not require the attacker to hold a valid RNDC key; only network access to the control channel's configured TCP port is necessary. This issue affects BIND 9 versions 9.2.0 through 9.16.43, 9.18.0 through 9.18.18, 9.19.0 through 9.19.16, 9.9.3-S1 through 9.16.43-S1, and 9.18.0-S1 through 9.18.18-S1.

Why

The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.

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 → Improperly Controlled Sequential Memory Allocation → 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-1325

CWE-1325: Improperly Controlled Sequential Memory Allocation. The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.

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-1325
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-0064Juniper Produkte: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter, anonymer, authentisierter, lokaler oder physischer Angreifer kann mehrere Schwachstellen in Juniper JUNOS, Juniper JUNOS Evolved, Juniper SRX Series, Juniper EX Series, Juniper QFX Series, Juniper ACX Series, Juniper PTX Series und Juniper MX Series ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen und seine Berechtigungen zu erweitern.

Official advisory
BSI · German · WID-SEC-W-2024-1591Juniper JUNOS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Privilegien zu erweitern und Sicherheitsmechanismen inklusive zu umgehen.

Official advisory
BSI · German · WID-SEC-W-2023-2412Internet Systems Consortium BIND: Mehrere Schwachstellen

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-2026-AVI-0287Multiples vulnérabilités dans les produits NetApp

De multiples vulnérabilités ont été découvertes dans les produits NetApp. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0630Multiples vulnérabilités dans IBM QRadar

ERecord?id=CVE-2022-25881 Référence CVE CVE-2022-25883 https://www.cve.org/CVERecord?id=CVE-2022-25883 Référence CVE CVE-2022-3517 https://www.cve.org/CVERecord?id=CVE-2022-3517 Référence CVE CVE-2022-37601 https://www.cve.org/CVERecord?id=CVE-2022-37601 Référence CVE CVE-2022-37603 https://www.cve.org/CVERecord?id=CVE-2022-37603 Référence CVE CVE-2022-43441 https://www.cve.org/CVERecord?id=CVE-2022-43441 Référence CVE CVE-2023-0361 https://www.cve.org/CVERecord?id=CVE-2023-0361 Référence CVE CVE-2023-0842 https://www.cve.org/CVERecord?id=CVE-2023-0842 Référence CVE CVE-2023-32233 https://www.cve.org/CVERecord?id=CVE-2023-32233 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-3446 https://www.cve.org/CVERecord?id=CVE-2023-3446 Référence CVE CVE-2023-35001 https://www.cve.org/CVERecord?id=CVE-2023-35001 Référence CVE CVE-2023-3609 https://www.cve.org/CVERecord?id=CVE-2023-3609 Référence CVE CVE-2023-36632 https://www.cve.org/CVERecord?id=CVE-2023-36632 Référence CVE CVE-2023-3817 https://www.cve.org/CVERecord?id=CVE-2023-3817 Référence CVE CVE-2023-38546 https://www.cve.org/CVERecord?id=CVE-2023-38546 Référence CVE CVE-2023-39615 https://www.cve.org/CVERecord?id=CVE-2023-39615 Référence CVE CVE-2023-40217 https://www.cve.org/CVERecord?id=CVE-202

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

Record?id=CVE-2023-2700 Référence CVE CVE-2023-27522 https://www.cve.org/CVERecord?id=CVE-2023-27522 Référence CVE CVE-2023-2828 https://www.cve.org/CVERecord?id=CVE-2023-2828 Référence CVE CVE-2023-30630 https://www.cve.org/CVERecord?id=CVE-2023-30630 Référence CVE CVE-2023-3090 https://www.cve.org/CVERecord?id=CVE-2023-3090 Référence CVE CVE-2023-32067 https://www.cve.org/CVERecord?id=CVE-2023-32067 Référence CVE CVE-2023-32360 https://www.cve.org/CVERecord?id=CVE-2023-32360 Référence CVE CVE-2023-32435 https://www.cve.org/CVERecord?id=CVE-2023-32435 Référence CVE CVE-2023-32439 https://www.cve.org/CVERecord?id=CVE-2023-32439 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-3390 https://www.cve.org/CVERecord?id=CVE-2023-3390 Référence CVE CVE-2023-34058 https://www.cve.org/CVERecord?id=CVE-2023-34058 Référence CVE CVE-2023-34059 https://www.cve.org/CVERecord?id=CVE-2023-34059 Référence CVE CVE-2023-34969 https://www.cve.org/CVERecord?id=CVE-2023-34969 Référence CVE CVE-2023-35001 https://www.cve.org/CVERecord?id=CVE-2023-35001 Référence CVE CVE-2023-35788 https://www.cve.org/CVERecord?id=CVE-2023-35788 Référence CVE CVE-2023-3611 https://www.cve.org/CVERecord?id=CVE-2023-3611 Référence CVE CVE-2023-37450 https://www.cve.org/CVERecord?id=CVE-2

Official advisory
CERT-FR · French · CERTFR-2024-AVI-0506Multiples vulnérabilités dans Juniper Secure Analytics

/CVERecord?id=CVE-2023-3138 Référence CVE CVE-2023-3141 https://www.cve.org/CVERecord?id=CVE-2023-3141 Référence CVE CVE-2023-31436 https://www.cve.org/CVERecord?id=CVE-2023-31436 Référence CVE CVE-2023-3161 https://www.cve.org/CVERecord?id=CVE-2023-3161 Référence CVE CVE-2023-3212 https://www.cve.org/CVERecord?id=CVE-2023-3212 Référence CVE CVE-2023-32324 https://www.cve.org/CVERecord?id=CVE-2023-32324 Référence CVE CVE-2023-32360 https://www.cve.org/CVERecord?id=CVE-2023-32360 Référence CVE CVE-2023-3268 https://www.cve.org/CVERecord?id=CVE-2023-3268 Référence CVE CVE-2023-33203 https://www.cve.org/CVERecord?id=CVE-2023-33203 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-33951 https://www.cve.org/CVERecord?id=CVE-2023-33951 Référence CVE CVE-2023-33952 https://www.cve.org/CVERecord?id=CVE-2023-33952 Référence CVE CVE-2023-34241 https://www.cve.org/CVERecord?id=CVE-2023-34241 Référence CVE CVE-2023-34966 https://www.cve.org/CVERecord?id=CVE-2023-34966 Référence CVE CVE-2023-34967 https://www.cve.org/CVERecord?id=CVE-2023-34967 Référence CVE CVE-2023-34968 https://www.cve.org/CVERecord?id=CVE-2023-34968 Référence CVE CVE-2023-3567 https://www.cve.org/CVERecord?id=CVE-2023-3567 Référence CVE CVE-2023-35823 https://www.cve.org/CVERecord?id=CVE

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

ord?id=CVE-2023-22081 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-26604 https://www.cve.org/CVERecord?id=CVE-2023-26604 Référence CVE CVE-2023-27043 https://www.cve.org/CVERecord?id=CVE-2023-27043 Référence CVE CVE-2023-2828 https://www.cve.org/CVERecord?id=CVE-2023-2828 Référence CVE CVE-2023-28322 https://www.cve.org/CVERecord?id=CVE-2023-28322 Référence CVE CVE-2023-28486 https://www.cve.org/CVERecord?id=CVE-2023-28486 Référence CVE CVE-2023-28487 https://www.cve.org/CVERecord?id=CVE-2023-28487 Référence CVE CVE-2023-32681 https://www.cve.org/CVERecord?id=CVE-2023-32681 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-34966 https://www.cve.org/CVERecord?id=CVE-2023-34966 Référence CVE CVE-2023-34967 https://www.cve.org/CVERecord?id=CVE-2023-34967 Référence CVE CVE-2023-34968 https://www.cve.org/CVERecord?id=CVE-2023-34968 Référence CVE CVE-2023-37920 https://www.cve.org/CVERecord?id=CVE-2023-37920 Référence CVE CVE-2023-38546 https://www.cve.org/CVERecord?id=CVE-2023-38546 Référence CVE CVE-2023-39615 https://www.cve.org/CVERecord?id=CVE-2023-39615 Référence CVE CVE-2023-4091 https://www.cve.org/CVERecord?id=CV

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

ecord?id=CVE-2023-23454 Référence CVE CVE-2023-23918 https://www.cve.org/CVERecord?id=CVE-2023-23918 Référence CVE CVE-2023-23920 https://www.cve.org/CVERecord?id=CVE-2023-23920 Référence CVE CVE-2023-24329 https://www.cve.org/CVERecord?id=CVE-2023-24329 Référence CVE CVE-2023-26464 https://www.cve.org/CVERecord?id=CVE-2023-26464 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-2828 https://www.cve.org/CVERecord?id=CVE-2023-2828 Référence CVE CVE-2023-32067 https://www.cve.org/CVERecord?id=CVE-2023-32067 Référence CVE CVE-2023-32360 https://www.cve.org/CVERecord?id=CVE-2023-32360 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-3446 https://www.cve.org/CVERecord?id=CVE-2023-3446 Référence CVE CVE-2023-36842 https://www.cve.org/CVERecord?id=CVE-2023-36842 Référence CVE CVE-2023-3817 https://www.cve.org/CVERecord?id=CVE-2023-3817 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2023-38802 https://www.cve.org/CVERecord?id=CVE-2023-38802 Référence CVE CVE-2024-21585 https://www.cve.org/CVERecord?id=CVE-2024-21585 Référence CVE CVE-2024-21587 https://www.cve.org/CVERecord?id=CVE-2024-21587 Référence CVE CVE-2024-21589 https://www.cve.org/CVERecord?id=CVE-2

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

ord?id=CVE-2022-40149 Référence CVE CVE-2022-40150 https://www.cve.org/CVERecord?id=CVE-2022-40150 Référence CVE CVE-2022-45685 https://www.cve.org/CVERecord?id=CVE-2022-45685 Référence CVE CVE-2022-45693 https://www.cve.org/CVERecord?id=CVE-2022-45693 Référence CVE CVE-2023-1436 https://www.cve.org/CVERecord?id=CVE-2023-1436 Référence CVE CVE-2023-22045 https://www.cve.org/CVERecord?id=CVE-2023-22045 Référence CVE CVE-2023-22049 https://www.cve.org/CVERecord?id=CVE-2023-22049 Référence CVE CVE-2023-26049 https://www.cve.org/CVERecord?id=CVE-2023-26049 Référence CVE CVE-2023-32233 https://www.cve.org/CVERecord?id=CVE-2023-32233 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE-2023-3341 Référence CVE CVE-2023-34040 https://www.cve.org/CVERecord?id=CVE-2023-34040 Référence CVE CVE-2023-35001 https://www.cve.org/CVERecord?id=CVE-2023-35001 Référence CVE CVE-2023-36478 https://www.cve.org/CVERecord?id=CVE-2023-36478 Référence CVE CVE-2023-36479 https://www.cve.org/CVERecord?id=CVE-2023-36479 Référence CVE CVE-2023-37920 https://www.cve.org/CVERecord?id=CVE-2023-37920 Référence CVE CVE-2023-40167 https://www.cve.org/CVERecord?id=CVE-2023-40167 Référence CVE CVE-2023-40787 https://www.cve.org/CVERecord?id=CVE-2023-40787 Référence CVE CVE-2023-41080 https://www.cve.org/CVERecord?id=C

Official advisory
CERT-FR · French · CERTFR-2023-AVI-0958Multiples vulnérabilités dans IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM . Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et une exécution de code arbitraire à distance.

Official advisory
CERT-FR · French · CERTFR-2023-AVI-0950Multiples vulnérabilités dans Juniper Secure Analytics

De multiples vulnérabilités ont été découvertes dans Juniper Secure Analytics . Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et un contournement de la politique de sécurité.

Official advisory
CERT-FR · French · CERTFR-2023-AVI-0767Multiples 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
ABB M2M Gateway ARM600, firmware versions >=4.1.2|<=5.0.3; ABB M2M Gateway SW, software versions >=5.0.1|<=5.0.3
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 3. ARM600 system is by default not dependent on the name service (DNS). If name service is not used in the system, the name service port (TCP/UDP port 53) can be blocked by a firewall. Refer to section General security recommendations for additional advice on how to keep your system secure.
04

Evidence and provenance

Published 20 Sept 2023 · Last source change 2 Dec 2025, 20:15 UTC · CWE-1325 · Improperly Controlled Sequential Memory Allocation

CVE recordCVE.org · 5.2
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-44009
Product sourceVendor CSAF · ABB Product Security Incident Response Team (PSIRT)
Remediation sourceVendor CSAF · ABB Product Security Incident Response Team (PSIRT)
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 →
  1. Vendor guidanceAuthoritative vendor guidance changed from authoritative remediation link to authoritative remediation link.
    Before
    authoritative remediation link
    After
    authoritative remediation link
    ABB Product Security Incident Response Team (PSIRT)
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-3341 · cve.blacktree.nl