BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-38408High confidence

n/a — Unquoted Search Path or Element

Unknown · Unknown

Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 79.70% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown Unknown and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-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.

8 package states
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 releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainopensshVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainopensshVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainopensshVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:9.3p2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:9.2p1-2+deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:9.3p2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceopensshVendor fix publishedDebian records a fixed source-package version for this release.1:9.3p2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveopenssh-ssh1Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 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.

4 current
SCA-2025-0011 · CSAF 2.0 · revision 1.0.0 · finalSICK PSIRTVulnerabilities affecting Endress+Hauser SSG-E210GC
1 known affected

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

  • Endress+Hauser SSG-E210GC all Firmware versions
Summary
The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.
Remediation
Please make sure that only trusted entities have access to the device. Furthermore, you should apply the following General Security Measures when operating the product to mitigate the associated security risk. The collected resources "SICK Operating Guidelines" and "ICS-CERT recommended practices on Industrial Security" could help to implement the general security practices.
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.
Remediation
Update to V3.1.5 or later version
SCA-2025-0009 · CSAF 2.0 · revision 1 · finalSICK PSIRTVulnerabilities affecting SICK TDC-E210GC
1 known affected

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

  • SICK TDC-E210GC all Firmware versions
Summary
The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.
Remediation
Please make sure that only trusted entities have access to the device. Furthermore, you should apply the following General Security Measures when operating the product to mitigate the associated security risk. The collected resources "SICK Operating Guidelines" and "ICS-CERT recommended practices on Industrial Security" could help to implement the general security practices.
2NGA002579 · CSAF 2.0 · revision 1 · finalABB Product Security Incident Response Team (PSIRT)CVE-2023-38408
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
Vulnerability in the PKCS#11 feature of ssh-agent in OpenSSH versions before 9.3p2. It involves an insufficiently trustworthy search path, which can lead to remote code execution if an agent is forwarded by authenticated user to an attacker-controlled system.
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. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-42225

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 actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 9 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.

What

The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.

Why

The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.

Why

The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Unquoted Search Path or Element → execute code or commands in the affected security context
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-428 ↗

CWE-428: Unquoted Search Path or Element. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path.

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:H/I:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-428Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-3195Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-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-2024-1082Juniper JUNOS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS im Zusammenhang mit OpenSSH ausnutzen, um Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen oder Dateien zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-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-2023-2679Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-2625IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand herbeizuführen und einen Cross-Site-Scripting-Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-2240IBM AIX: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen in IBM AIX und IBM VIOS ausnutzen, um Informationen offenzulegen oder um beliebigen Code auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-1843OpenBSD: Schwachstelle ermöglicht Codeausführung

Ein entfernter Angreifer kann eine Schwachstelle in OpenBSD ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-1819OpenSSH: Schwachstelle ermöglicht Codeausführung

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in OpenSSH ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-013[Control Systems] Moxa security advisory (AV26-013)

On January 9, 2026, Moxa published a security advisory to address a critical vulnerability in the following products:

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20230726Security Bulletin 26 Jul 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 26 Jul 2023, published on 26 July 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0016Vulnérabilité dans les produits Moxa

Une vulnérabilité a été découverte dans les produits Moxa. Elle permet à un attaquant de provoquer une exécution de code arbitraire à distance.

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

CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-3090 https://www.cve.org/CVERecord?id=CVE-2023-3090 Référence CVE CVE-2023-31248 https://www.cve.org/CVERecord?id=CVE-2023-31248 Référence CVE CVE-2023-32233 https://www.cve.org/CVERecord?id=CVE-2023-32233 Référence CVE CVE-2023-3390 https://www.cve.org/CVERecord?id=CVE-2023-3390 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-3610 https://www.cve.org/CVERecord?id=CVE-2023-3610 Référence CVE CVE-2023-3776 https://www.cve.org/CVERecord?id=CVE-2023-3776 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2023-38575 https://www.cve.org/CVERecord?id=CVE-2023-38575 Référence CVE CVE-2023-39368 https://www.cve.org/CVERecord?id=CVE-2023-39368 Référence CVE CVE-2023-4004 https://www.cve.org/CVERecord?id=CVE-2023-4004 Référence CVE CVE-2023-4147 https://www.cve.org/CVERecord?id=CVE-2023-4147 Référence CVE CVE-2023-43490 https://www.cve.org/CVERecord?id=CVE-2023-43490 Référence CVE CVE-2023-43785 https://www.cve.org/CVERecord?id=CVE-2023-43785 Référence CVE CVE-2023-43786 https://www.cve.org/CVERecord?id=CVE-2023-43786 Référence CVE CVE-2023-43787 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1018Multiples vulnérabilités dans les produits Qnap

tps://www.qnap.com/go/security-advisory/qsa-24-40 Bulletin de sécurité Qnap QSA-24-43 du 23 novembre 2024 https://www.qnap.com/go/security-advisory/qsa-24-43 Bulletin de sécurité Qnap QSA-24-44 du 23 novembre 2024 https://www.qnap.com/go/security-advisory/qsa-24-44 Bulletin de sécurité Qnap QSA-24-46 du 23 novembre 2024 https://www.qnap.com/go/security-advisory/qsa-24-46 Bulletin de sécurité Qnap QSA-24-47 du 23 novembre 2024 https://www.qnap.com/go/security-advisory/qsa-24-47 Référence CVE CVE-2020-14145 https://www.cve.org/CVERecord?id=CVE-2020-14145 Référence CVE CVE-2021-41617 https://www.cve.org/CVERecord?id=CVE-2021-41617 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2024-32767 https://www.cve.org/CVERecord?id=CVE-2024-32767 Référence CVE CVE-2024-32768 https://www.cve.org/CVERecord?id=CVE-2024-32768 Référence CVE CVE-2024-32769 https://www.cve.org/CVERecord?id=CVE-2024-32769 Référence CVE CVE-2024-32770 https://www.cve.org/CVERecord?id=CVE-2024-32770 Référence CVE CVE-2024-37041 https://www.cve.org/CVERecord?id=CVE-2024-37041 Référence CVE CVE-2024-37042 https://www.cve.org/CVERecord?id=CVE-2024-37042 Référence CVE CVE-2024-37043 https://www.cve.org/CVERecord?id=CVE-2024-37043 Référence CVE CVE-2024-37044 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0378Multiples vulnérabilités dans Juniper Junos OS

De multiples vulnérabilités ont été découvertes dans Juniper Junos OS. Certaines d'entre elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur, une exécution de code arbitraire à distance et un déni de service à distance.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0297Multiples vulnérabilités dans Juniper

ecord?id=CVE-2023-27043 Référence CVE CVE-2023-28366 https://www.cve.org/CVERecord?id=CVE-2023-28366 Référence CVE CVE-2023-29491 https://www.cve.org/CVERecord?id=CVE-2023-29491 Référence CVE CVE-2023-32681 https://www.cve.org/CVERecord?id=CVE-2023-32681 Référence CVE CVE-2023-32731 https://www.cve.org/CVERecord?id=CVE-2023-32731 Référence CVE CVE-2023-32732 https://www.cve.org/CVERecord?id=CVE-2023-32732 Référence CVE CVE-2023-3446 https://www.cve.org/CVERecord?id=CVE-2023-3446 Référence CVE CVE-2023-3592 https://www.cve.org/CVERecord?id=CVE-2023-3592 Référence CVE CVE-2023-36054 https://www.cve.org/CVERecord?id=CVE-2023-36054 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2023-38545 https://www.cve.org/CVERecord?id=CVE-2023-38545 Référence CVE CVE-2023-38546 https://www.cve.org/CVERecord?id=CVE-2023-38546 Référence CVE CVE-2023-3978 https://www.cve.org/CVERecord?id=CVE-2023-3978 Référence CVE CVE-2023-39975 https://www.cve.org/CVERecord?id=CVE-2023-39975 Référence CVE CVE-2023-40217 https://www.cve.org/CVERecord?id=CVE-2023-40217 Référence CVE CVE-2023-41913 https://www.cve.org/CVERecord?id=CVE-2023-41913 Référence CVE CVE-2023-43804 https://www.cve.org/CVERecord?id=CVE-2023-43804 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CV

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

g/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-2024-21589 Référence CVE CVE-2024-21591 https://www.cve.org/CVERecord?id=CVE-2024-21591 Référence CVE CVE-2024-21594 https://www.cve.org/CVERecord?id=CVE-2024-21594 Référence CVE CVE-2024-21595 https://www.cve.org/CVERecord?id=CVE-2024-21595 Référence CVE CVE-2024-21596 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-1015Multiples vulnérabilités dans les produits Siemens

/CVERecord?id=CVE-2023-3446 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-35945 https://www.cve.org/CVERecord?id=CVE-2023-35945 Référence CVE CVE-2023-3609 https://www.cve.org/CVERecord?id=CVE-2023-3609 Référence CVE CVE-2023-3611 https://www.cve.org/CVERecord?id=CVE-2023-3611 Référence CVE CVE-2023-3772 https://www.cve.org/CVERecord?id=CVE-2023-3772 Référence CVE CVE-2023-3817 https://www.cve.org/CVERecord?id=CVE-2023-3817 Référence CVE CVE-2023-38380 https://www.cve.org/CVERecord?id=CVE-2023-38380 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2023-38545 https://www.cve.org/CVERecord?id=CVE-2023-38545 Référence CVE CVE-2023-38546 https://www.cve.org/CVERecord?id=CVE-2023-38546 Référence CVE CVE-2023-39128 https://www.cve.org/CVERecord?id=CVE-2023-39128 Référence CVE CVE-2023-39189 https://www.cve.org/CVERecord?id=CVE-2023-39189 Référence CVE CVE-2023-39192 https://www.cve.org/CVERecord?id=CVE-2023-39192 Référence CVE CVE-2023-39193 https://www.cve.org/CVERecord?id=CVE-2023-39193 Référence CVE CVE-2023-39194 https://www.cve.org/CVERecord?id=CVE-2023-39194 Référence CVE CVE-2023-39615 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0926Multiples 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 exécution de code arbitraire à distance et une atteinte à la confidentialité des données.

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

d?id=CVE-2023-33850 Référence CVE CVE-2023-34149 https://www.cve.org/CVERecord?id=CVE-2023-34149 Référence CVE CVE-2023-34396 https://www.cve.org/CVERecord?id=CVE-2023-34396 Référence CVE CVE-2023-34453 https://www.cve.org/CVERecord?id=CVE-2023-34453 Référence CVE CVE-2023-34454 https://www.cve.org/CVERecord?id=CVE-2023-34454 Référence CVE CVE-2023-34455 https://www.cve.org/CVERecord?id=CVE-2023-34455 Référence CVE CVE-2023-34981 https://www.cve.org/CVERecord?id=CVE-2023-34981 Référence CVE CVE-2023-35012 https://www.cve.org/CVERecord?id=CVE-2023-35012 Référence CVE CVE-2023-35116 https://www.cve.org/CVERecord?id=CVE-2023-35116 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2023-39976 https://www.cve.org/CVERecord?id=CVE-2023-39976 Référence CVE CVE-2023-40367 https://www.cve.org/CVERecord?id=CVE-2023-40367 Gestion détaillée du document le 13 octobre 2023 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0757Multiples vulnérabilités dans IBM Spectrum Copy Data Management

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

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

ord?id=CVE-2023-21939 Référence CVE CVE-2023-21954 https://www.cve.org/CVERecord?id=CVE-2023-21954 Référence CVE CVE-2023-21967 https://www.cve.org/CVERecord?id=CVE-2023-21967 Référence CVE CVE-2023-2283 https://www.cve.org/CVERecord?id=CVE-2023-2283 Référence CVE CVE-2023-22998 https://www.cve.org/CVERecord?id=CVE-2023-22998 Référence CVE CVE-2023-23454 https://www.cve.org/CVERecord?id=CVE-2023-23454 Référence CVE CVE-2023-24329 https://www.cve.org/CVERecord?id=CVE-2023-24329 Référence CVE CVE-2023-28466 https://www.cve.org/CVERecord?id=CVE-2023-28466 Référence CVE CVE-2023-32233 https://www.cve.org/CVERecord?id=CVE-2023-32233 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2023-40371 https://www.cve.org/CVERecord?id=CVE-2023-40371 Gestion détaillée du document le 25 août 2023 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0572Vulnérabilité dans OpenSSH

Une vulnérabilité a été découverte dans OpenSSH. Elle permet à un attaquant de provoquer une exécution de code arbitraire à distance.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-020641OpenBSD の OpenSSH 等複数ベンダの製品における引用されない検索パスまたは要素に関する脆弱性

OpenBSD の OpenSSH 等複数ベンダの製品には、引用されない検索パスまたは要素に関する脆弱性が存在します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5961OpenSSH 제품 보안 업데이트 권고

OpenSSH의 ssh-agent에서 PKCS#11 로드 요청 시 발생하는 원격 코드 실행 취약점 (CVE-2023-38408) [2]

Official advisory ↗
NCSC-NL · Dutch · NCSC-2024-0414Kwetsbaarheden verholpen in Oracle Communications

Een kwaadwillende kan de kwetsbaarheden misbruiken om aanvallen uit te voeren die kunnen leiden tot de volgende categorieën schade: - Denial-of-Service (DoS) - Manipuleren van gegevens - Uitvoer van willekeurige code (Gebruikersrechten) - Uitvoer van willekeurige code (Administratorrechten) - Toegang tot gevoelige gegevens

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.
Fix availability varies by product
Affected
Endress+Hauser SSG-E210GC all Firmware versions
Fixed
Update to V3.1.5 or later version
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
Please make sure that only trusted entities have access to the device. Furthermore, you should apply the following General Security Measures when operating the product to mitigate the associated security risk. The collected resources "SICK Operating Guidelines" and "ICS-CERT recommended practices on Industrial Security" could help to implement the general security practices.
04

Evidence and provenance

Published 20 Jul 2023 · Last source change 15 Oct 2024, 18:33 UTC · CWE-428 · Unquoted Search Path or Element

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
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-42225
Product sourceVendor CSAF · SICK PSIRT
Remediation sourceVendor CSAF · SICK PSIRT
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

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: sick.com/sca-2025-0011.json; removed remediation: endress.com.
    Before
    remediation: endress.com
    After
    remediation: sick.com/sca-2025-0011.json
    SICK PSIRT ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    n/a · 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.
    After
    n/a · Fixed: Update to V3.1.5 or later version
    Siemens ProductCERT ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf; removed remediation: sick.com/psirt.
    Before
    remediation: sick.com/psirt
    After
    remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf
    SICK PSIRT ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added remediation: search.abb.com/Download.aspx?DocumentID=2NGA002579&LanguageCode=en&DocumentPartId=pdf&Action=Launch; removed remediation: nvd.nist.gov/CVE-2023-38408.
    Before
    remediation: nvd.nist.gov/CVE-2023-38408
    After
    remediation: search.abb.com/Download.aspx?DocumentID=2NGA002579&LanguageCode=en&DocumentPartId=pdf&Action=Launch
    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-38408 · cve.blacktree.nl