dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-23386

HIGH · 7.8 CVSS v3.1 Published 2025-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
A Incorrect Default Permissions vulnerability in the openSUSE Tumbleweed package gerbera allows the service user gerbera to escalate to root.,This issue affects gerbera on openSUSE Tumbleweed before 2.5.0-1.1.

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

The gerbera media server package in openSUSE Tumbleweed ships with incorrect default file or service permissions that allow the gerbera service user account to perform local privilege escalation to root. This is a local vector vulnerability requiring authenticated access to the gerbera user account.

MitigationUpgrade gerbera package to version 2.5.0-1.1 or later in openSUSE Tumbleweed, which corrects the default permissions to prevent root escalation. Alternatively, manually review and restrict file/directory permissions owned by the gerbera user to least-privilege principles.

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

CVSS:3.1/AV:L/AC:L/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 gerbera package version
    Run 'rpm -q gerbera' or 'zypper se gerbera' to check if the package is installed and its version
    Affected if Version is installed and is earlier than 2.5.0-1.1
  2. Verify gerbera user exists
    Run 'id gerbera' or check /etc/passwd for the gerbera user account
    Affected if The gerbera user account exists on the system
  3. Check gerbera service file permissions
    Examine permissions on service files in /etc/, /usr/lib/, or systemd service files: 'ls -la /etc/systemd/system/gerbera.service' or similar paths
    Affected if Service files are owned by gerbera or have overly permissive permissions (world-writable, group-writable, or setuid bits)
  4. Inspect gerbera data directory permissions
    Check ownership and permissions on directories typically used by gerbera such as /var/lib/gerbera, /var/cache/gerbera, /var/log/gerbera: 'ls -laR /var/lib/gerbera'
    Affected if Directories are owned by gerbera user and have permissions allowing the gerbera user to modify files that could lead to privilege escalation (e.g., world-writable scripts, config files, or directories in PATH)
  5. Search for SUID/SGID files owned by gerbera
    Run 'find / -user gerbera \( -perm -4000 -o -perm -2000 \) 2>/dev/null' to find any SUID/SGID files owned by the gerbera user
    Affected if Any SUID or SGID files are found owned by the gerbera user, indicating potential escalation vectors

The system is affected if gerbera package version is before 2.5.0-1.1 and the gerbera user owns files or directories with permissions that could enable local 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.

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

Upgrade gerbera package to version 2.5.0-1.1 or later in openSUSE Tumbleweed, which corrects the default permissions to prevent root escalation. Alternatively, manually review and restrict file/directory permissions owned by the gerbera user to least-privilege principles.

Recommended fix High confidence

gerbera version 2.5.0-1.1 or later on openSUSE Tumbleweed

  1. Run 'sudo zypper refresh' to update the package metadata
  2. Run 'sudo zypper update gerbera' to upgrade gerbera to the fixed version
  3. After the update completes, restart the gerbera service with 'sudo systemctl restart gerbera' or reboot the system to ensure the new permissions are applied

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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