Sauter Devices
CVE-2025-41721
LOW
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as high-privileged operator
-
ExploitAdd password-protected self-signed certificate with crafted parameters
-
ExecutionUnneutralized special elements passed to openssl command
-
ImpactLimited integrity compromise via command injection
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires high-privileged authenticated access to the affected Sauter device's management interface (PR:H); it is not reachable by anonymous or low-privileged users. The specific trigger is the certificate-management workflow for adding a password-protected self-signed certificate, where special elements in the supplied parameters are not neutralized before being passed to the openssl command. Limiting factors: the attacker must already be an administrative/high-privilege operator (restricting realistic abuse to malicious insiders or post-compromise escalation), the action is confined to the certificate-add feature, and impact is integrity-only (C:N/A:N), so no data disclosure or denial of service results. |
| Impact | This is a genuinely LOW-priority issue, and the signals are consistent rather than conflicting. The CVSS 3.1 base score is 2.7 with vector AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N - network-reachable and low-complexity, but gated behind PR:H (high privileges), with only partial integrity impact and no confidentiality or availability impact. EPSS reinforces this: 0.20% probability at the 9th percentile indicates very low expected exploitation activity. There is no CISA KEV listing and no public exploit identified, so exploitation status is 'no public exploit identified at time of analysis.' Mapping to an SSVC-style frame: exploitation = none, automatable = no (an attacker must already be a privileged, authenticated operator and interact with a certificate-management workflow), and technical impact = partial (integrity-only, I:L). The one thing to note is the product scope: the 'OpenSSL' tag could be misread as the OpenSSL library itself, but the vendor reference (sauter.csaf-tp.certvde.com, CERT@VDE advisory VDE-2025-060) and the description make clear the flaw is command-argument injection into an invocation of the openssl CLI within a Sauter product - not a vulnerability in OpenSSL. Net: a high-CVSS illusion is not present here; this is a correctly-scored low-severity, privilege-gated issue best treated as hardening rather than an emergency. |
| Exploit ScenarioDerived | An attacker who already holds high-privileged (administrative) authenticated access to the affected Sauter device's management interface adds a password-protected self-signed certificate, embedding special shell/command elements in the supplied parameters (e.g., the password or certificate fields). Because these elements are not neutralized before being passed to the openssl command, the injected input is interpreted by the command, yielding limited (integrity-only) command injection. No public proof-of-concept or exploit code has been identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 18, 2026
Sauter device administrators can inject unintended arguments into the OpenSSL invocation used by the password-protected self-signed certificate workflow, allowing integrity-impacting manipulation of the generated certificate or command behavior. The issue is reachable only through the management interface by an already high-privileged authenticated user (CVSS 2.7, PR:H), and no public exploit code or CISA KEV entry was identified at time of analysis; EPSS is only 0.20% (9th percentile), consistent with a low-priority insider or post-compromise risk.
RemediationAI
No vendor-released patch or fixed firmware version is identified in the provided data; consult CERT VDE advisory VDE-2025-060 at https://sauter.csaf-tp.certvde.com/.well-known/csaf/white/2025/vde-2025-060.json for the authoritative update status. Until a vendor fix is available, restrict the device management interface to a trusted administrative VLAN or firewall allowlist (trade-off: reduces remote administration convenience) and enforce least privilege so only essential administrators can perform certificate management (trade-off: may slow legitimate certificate operations). If the password-protected self-signed certificate workflow is not required, disable or tightly restrict that feature during maintenance windows (trade-off: blocks legitimate self-signed certificate onboarding), and monitor management logs and certificate stores for unexpected changes. Client-side validation alone is insufficient because the vulnerability is in server-side OpenSSL command construction.
Affected ProductsAI
Sauter devices exposing the certificate-management workflow for adding a password-protected self-signed certificate are affected. The provided intelligence does not enumerate specific model numbers, firmware versions, or CPE identifiers; the authoritative affected-product matrix should be taken from the CERT VDE advisory VDE-2025-060 at https://sauter.csaf-tp.certvde.com/.well-known/csaf/white/2025/vde-2025-060.json.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-77 command injection in the certificate-management path that builds an OpenSSL command line for creating a password-protected self-signed certificate. Special elements in the supplied password or related certificate parameters are not neutralized before being passed to the openssl process, so an attacker who controls those values may alter OpenSSL options or arguments. Because the assessed impact is integrity-only (C:N/I:L/A:N), the realistic effect is parameter/option manipulation within the certificate operation rather than arbitrary code execution or data disclosure. The network vector (AV:N) applies to the device management interface, but the high-privilege prerequisite (PR:H) confines abuse to administrators or attackers who have already compromised an administrative account. No CPE strings or firmware version ranges were supplied in the available data, so the exact affected model/firmware matrix cannot be confirmed from the input alone.
Know when OpenSSL gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Network-accessible management interface (AV:N/AC:L) but requires administrative privileges to reach the certificate feature (PR:H), and injection into the openssl invocation yields only partial integrity impact (I:L), with no confidentiality or availability effect.
Primary rating from Vendor (cert).
CVSS VectorVendor: cert
DescriptionCVE.org
A high privileged remote attacker can influence the parameters passed to the openssl command due to improper neutralization of special elements when adding a password protected self-signed certificate.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Rated cri
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas
The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB