dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-53396

HIGH · 7.0 CVSS v3.0 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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
Incorrect permission assignment for critical resource issue exists in SS1 Ver.16.0.0.10 and earlier (Media version:16.0.0a and earlier), which may allow users who can log in to a client terminal to obtain root privileges.

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

A local privilege escalation vulnerability exists in SS1 versions 16.0.0.10 and earlier (Media version 16.0.0a and earlier) due to incorrect permission assignment on a critical resource. An authenticated user with client terminal access can exploit this misconfiguration to obtain root privileges.

MitigationApply the vendor patch to upgrade SS1 to a version later than 16.0.0.10 (or Media version later than 16.0.0a) and verify correct permissions on critical system resources.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:H/PR:L/UI:N/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 SS1 version
    Run the command or check the package manager to determine the installed SS1 version (for example: ss1 --version, or check the installed package metadata)
    Affected if The version is 16.0.0.10 or earlier
  2. Identify Media version
    Run the command or check the package manager to determine the installed Media version (for example: media --version, or check the installed package metadata)
    Affected if The version is 16.0.0a or earlier
  3. Verify authenticated client terminal access exists
    Confirm whether client terminal access is enabled or available for non-root users in the SS1 environment configuration
    Affected if Client terminal access is enabled for authenticated users
  4. Inspect critical resource permissions
    Examine file or system resource permissions on critical SS1 components (such as system binaries, configuration files, or privileged execution paths) that the vendor has identified as having incorrect assignments
    Affected if Permissions on critical resources are set too permissively (for example, world-writable or writable by low-privileged users)

A user is affected if they run SS1 version 16.0.0.10 / Media 16.0.0a or earlier, have client terminal access enabled, and possess incorrect permissions on critical resources that enable privilege escalation to root.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch to upgrade SS1 to a version later than 16.0.0.10 (or Media version later than 16.0.0a) and verify correct permissions on critical system resources.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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