Sinec Network Management SystemApplication · Siemens

CVE-2022-25311

HIGH · 7.3 CVSS v3.1 Published 2022-03-08
Fix available
A fix is available. Upgrade to 1.0.3 or later.
See remediation →
73/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 SINEC NMS (All versions >= V1.0.3 < V2.0), SINEC NMS (All versions < V1.0.3), SINEMA Server V14 (All versions). The affected software do not properly check privileges between users during the same web browser session, creating an unintended sphere of control. This could allow an authenticated low privileged user to achieve privilege escalation.

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 · moderate confidence

This is a session-based privilege escalation vulnerability where the affected web applications (SINEC NMS and SINEMA Server V14) fail to properly re-validate user privileges during the same browser session. An authenticated low-privileged user can exploit this flaw to gain higher-level administrative privileges, bypassing intended access controls.

MitigationApply vendor-supplied patches or updates from Siemens security advisories. Until patched, implement strict session management controls, enforce re-authentication for privilege-sensitive operations, and consider network segmentation to limit exposure.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sinec Network Management SystemApplication
Affected:< 1.0.3
Sinema ServerApplication
Affected:= 14.0

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
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Identify installed Siemens SINEC NMS version
    Locate the SINEC NMS installation directory and check the version information file, typically found in the application directory or via the web interface login page version display
    Affected if Installed version is lower than 1.0.3
  2. Identify installed Siemens Sinema Server version
    Check the Sinema Server application version through the server management interface or application documentation
    Affected if Installed version is exactly 14.0
  3. Verify session privilege validation behavior
    Log in with a low-privileged user account, perform standard operations, then attempt to access administrative functions or URLs directly within the same session without re-authenticating
    Affected if Administrative functions are accessible without prompting for credentials or re-authentication
  4. Check for privilege escalation via session
    After logging in as a non-admin user, use browser developer tools to examine session cookies, then attempt to directly access admin-specific endpoints or trigger admin-only actions within the same authenticated session
    Affected if Low-privilege session can perform administrator-level actions without additional credential verification

User is affected if either SINEC NMS version is below 1.0.3 or Sinema Server version is exactly 14.0, AND a low-privileged user session can access or execute administrative functions without re-authentication

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
Upgrade available Upgrade to 1.0.3 or later
Fixed in 1.0.3
Interim mitigation

Apply vendor-supplied patches or updates from Siemens security advisories. Until patched, implement strict session management controls, enforce re-authentication for privilege-sensitive operations, and consider network segmentation to limit exposure.

Recommended fix High confidence

SINEC NMS: V2.0 or later; SINEMA Server: latest available version

  1. 1. Identify the currently installed version of SINEC NMS or SINEMA Server using the system administration console or version check utility.
  2. 2. For SINEC NMS: Upgrade to version V2.0 or later, as all versions prior to V2.0 are affected by this privilege escalation vulnerability.
  3. 3. For SINEMA Server V14: Upgrade to the latest available version or apply vendor-supplied patch if available.
  4. 4. After upgrade, verify the new version number matches the target fixed release.
  5. 5. Test that privilege checks function correctly between different user sessions and roles.
  6. 6. Confirm low-privileged users can no longer escalate privileges within the same browser session.
Caveat Upgrading major versions may require configuration migration or compatibility testing with existing integrations

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

Fix this in Sinec Network Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2022-25311 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