dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-0416

HIGH · 8.9 CVSS v4.0 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
Zero-click

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
Local privilege escalation through insecure DCOM configuration in Valmet DNA versions prior to C2023. The DCOM object Valmet DNA Engineering has permissions that allow it to run commands as a user with the SeImpersonatePrivilege privilege. The SeImpersonatePrivilege privilege is a Windows permission that allows a process to impersonate another user. An attacker can use this vulnerability to escalate their privileges and take complete control of the system.

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

Local privilege escalation vulnerability in Valmet DNA industrial control software. The DCOM object 'Valmet DNA Engineering' has insecure permissions allowing command execution with SeImpersonatePrivilege, enabling an attacker with local access to impersonate privileged users and gain full system control.

MitigationUpgrade to Valmet DNA C2023 or later to obtain the patched version, or if upgrading is not immediately feasible, review and restrict the DCOM permissions on the Valmet DNA Engineering object to remove excessive privileges.

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
Adjacent
Complexity
Low
Privileges
Low
Authentication
Y
User interaction
None
Scope
N

CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:D/RE:H/U:Amber

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. Verify Valmet DNA Engineering installation
    Check for Valmet DNA Engineering in Windows Programs and Features, or search for Valmet DNA-related files in Program Files
    Affected if Valmet DNA Engineering is present and version is before C2023
  2. Identify Valmet DNA DCOM object
    Run 'dcomcnfg' (Component Services), expand Computers > My Computer > DCOM Config, look for 'ValmetDNA' or 'Valmet DNA Engineering' object
    Affected if The Valmet DNA DCOM object exists and is configured with default permissions
  3. Check DCOM launch permissions
    In dcomcnfg, right-click the Valmet DNA DCOM object > Properties > Security > Launch and Activation Permissions, check if 'Everyone' or untrusted users have Allow access
    Affected if Non-admin users or untrusted accounts have Launch or Activation permission
  4. Verify SeImpersonatePrivilege presence
    Run 'whoami /priv' in command prompt, look for 'SeImpersonatePrivilege' in the Enabled column
    Affected if The user context running the attack has SeImpersonatePrivilege enabled (typically available to service accounts, IIS users, and admin-level accounts)
  5. Check for SYSTEM-level Valmet DNA services
    Open Services console, look for Valmet DNA-related services running under SYSTEM or high-privilege accounts
    Affected if Valmet DNA services run with elevated privileges that could be impersonated

If Valmet DNA Engineering is installed with version before C2023 AND the DCOM object allows launch access to untrusted users, and those users have SeImpersonatePrivilege, the environment is vulnerable to privilege escalation.

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 Valmet DNA C2023 or later to obtain the patched version, or if upgrading is not immediately feasible, review and restrict the DCOM permissions on the Valmet DNA Engineering object to remove excessive privileges.

Recommended fix Moderate confidence

Valmet DNA C2023

  1. 1. Identify the current Valmet DNA version installed on the system
  2. 2. Plan and schedule an upgrade to Valmet DNA C2023 or later following change management procedures
  3. 3. Create a complete backup of the system including databases, configurations, and project files
  4. 4. Review Valmet upgrade documentation and release notes for C2023
  5. 5. Perform the upgrade to Valmet DNA C2023
  6. 6. After upgrade, verify the DCOM object 'Valmet DNA Engineering' permissions have been corrected by checking it no longer allows unauthorized impersonation
  7. 7. Test that normal Valmet DNA functionality operates correctly post-upgrade
Caveat Review C2023 release notes for any compatibility changes with existing configurations or integrations

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0416 — 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-0416 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