CyberSecBulletin
CVE-2025-30033NVD status: Deferred

Automation License Manager V6.0: Uncontrolled Search Path Element

Published Updated By the CyberSecBulletin desk

CVE-2025-30033 is a high-severity uncontrolled search path element vulnerability in Automation License Manager V6.0 from Siemens, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected Automation License Manager V6.0 versions: all versions. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Automation License Manager V6.2 to V6.2 Upd3 or a later version.
  2. Update Create MyConfig (CMC) to V6.9 or a later version.
  3. Update MultiFieldbus Configuration Tool (MFCT) to V1.5.5.0 or a later version.
  4. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
SiemensAutomation License Manager V6.0all versionsNot stated
SiemensAutomation License Manager V6.2before V6.2 Upd3V6.2 Upd3
SiemensCEMAT V10.0all versionsNot stated
SiemensCP PtP Param configuring interfaceall versionsNot stated
SiemensCreate MyConfig (CMC)before V6.9V6.9
SiemensEnergy Support Library (EnSL)all versionsNot stated
SiemensFM Configuration Packageall versionsNot stated
SiemensModular PID CTRL Toolall versionsNot stated
SiemensMultiFieldbus Configuration Tool (MFCT)before V1.5.5.0V1.5.5.0
SiemensOpenPCS 7 V10.0all versionsNot stated
SiemensOpenPCS 7 V9.1all versionsNot stated
SiemensSiemens Network Planner (SINETPLAN)before V2.0 SP2V2.0 SP2
SiemensSIMATIC Automation Toolbefore V5.0 SP4V5.0 SP4
SiemensSIMATIC Automation Tool SDK Windowsbefore V5.0 SP4V5.0 SP4
SiemensSIMATIC BATCH V10.0all versionsNot stated
SiemensSIMATIC BATCH V9.1all versionsNot stated
SiemensSIMATIC Control Function Library (CFL) V1.xall versionsNot stated
SiemensSIMATIC Control Function Library (CFL) V2.xall versionsNot stated
SiemensSIMATIC Control Function Library (CFL) V3.xbefore V3.1.0.2V3.1.0.2
SiemensSIMATIC Control Function Library (CFL) V4.xbefore V4.1V4.1
SiemensSIMATIC D7-SYSbefore V10.0 SP1V10.0 SP1
SiemensSIMATIC eaSie Core Package (6DL5424-0AX00-0AV8)all versionsNot stated
SiemensSIMATIC eaSie Document Skills V26all versionsNot stated
SiemensSIMATIC eaSie PCS 7 Skill Package V26 (6DL5424-0BX00-0AV8)all versionsNot stated
SiemensSIMATIC eaSie Workflow Skills V26all versionsNot stated

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (siemens.com).

Scoring systemScoreSeverityScored by
CVSS 4.08.5HighCNA (siemens.com)
CVSS 3.17.8HighCNA (siemens.com)

Official description

The affected setup component is vulnerable to DLL hijacking. This could allow an attacker to execute arbitrary code when a legitimate user installs an application that uses the affected setup component.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncontrolled Search Path Element

The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.

How developers prevent this class of flaw

  • Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
  • When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames. The portability can be improved by locating the full-qualified paths in a centralized, easily-modifiable location within the source code, and having the code refer to these paths.
  • Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.

More Uncontrolled Search Path Element vulnerabilities (CWE-427)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Automation License Manager V6.0

All Automation License Manager V6.0 vulnerabilities

Recent Uncontrolled Search Path Element vulnerabilities

Spotted an error? Tell us.