dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-29999

MEDIUM · 6.7 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in Siemens License Server (SLS) (All versions < V4.3). The affected application searches for executable files in the application folder without proper validation. This could allow an attacker to execute arbitrary code with administrative privileges by placing a malicious executable in the same directory.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Siemens License Server searches for executable files in its application folder without proper path validation, allowing an attacker with write access to the directory to place a malicious executable that will be executed with administrative privileges.

MitigationUpgrade to Siemens License Server V4.3 or later, and ensure the application directory has strict access controls to prevent unauthorized file placement.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Siemens License Server is installed
    Check Windows Services for 'Siemens License Server' or look in Programs and Features for entries containing 'Siemens License Server' or 'Sentinel License Server'
    Affected if The software is not found, indicating it is not installed
  2. Locate the License Server installation directory
    Right-click the service in Services.msc, go to Properties, and check the 'Path to executable' field; or check the installation directory in Programs and Features
    Affected if Installation directory cannot be determined or the software is not present
  3. Identify the installed version
    Right-click the executable in the installation path, select Properties, and check the 'File version' or 'Product version' field on the Details tab; alternatively, check the Windows registry under HKLM\SOFTWARE\Siemens\Sentinel_License_Server\CurrentVersion for the Version value
    Affected if Version is found to be earlier than V4.3 (such as V4.2, V4.1, V4.0, or earlier)
  4. Verify directory permissions
    Right-click the installation folder, select Properties, go to the Security tab, and examine which users or groups have 'Write' or 'Modify' permissions; use icacls <folderpath> from an elevated command prompt for detailed permission listing
    Affected if Users other than Administrators or system administrators have Write or Modify access to the application directory, allowing unauthorized file placement

You are affected if Siemens License Server is installed with a version earlier than V4.3 AND the application directory grants write access to non-administrative users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Siemens License Server V4.3 or later, and ensure the application directory has strict access controls to prevent unauthorized file placement.

Recommended fix High confidence

Siemens License Server V4.3

  1. 1. Back up the current Siemens License Server configuration and data directory before upgrading.
  2. 2. Navigate to the Siemens CERT portal (cert-portal.siemens.com) to obtain the fixed version.
  3. 3. Download Siemens License Server version V4.3 or later.
  4. 4. Stop the currently running SLS service.
  5. 5. Install or upgrade to the downloaded V4.3 version following Siemens installation documentation.
  6. 6. Restart the SLS service.
  7. 7. Verify that the application no longer searches for or executes unsigned executables from the application directory.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29999 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data