dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2025-41664

HIGH · 7.5 CVSS v3.1 Published 2025-09-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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 low-privileged remote attacker could gain unauthorized access to critical resources, such as firmware and certificates, due to improper permission handling during the runtime of services (e.g., FTP/SFTP). This access could allow the attacker to escalate privileges and modify firmware.

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 an improper permission handling vulnerability in services running during runtime (e.g., FTP/SFTP). A low-privileged remote attacker can bypass permission checks to access critical resources like firmware and certificates, enabling privilege escalation and firmware modification.

MitigationReview and fix permission handling code in runtime services (FTP/SFTP) to enforce proper access controls on sensitive resources like firmware and certificates. Implement principle of least privilege for all service operations.

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

CVSS:3.1/AV:N/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 running FTP/SFTP services
    Check for running processes: on Linux use 'ps aux | grep -E "(ftpd|sftpd|sshd|vsftpd|proftpd)"' or 'systemctl list-units --type=service | grep -E "(ftp|sftp|ssh)"'. On Windows check services.msc for FTP/SSH services.
    Affected if FTP or SFTP services are running and accessible to network users
  2. Determine the FTP/SFTP service version
    Identify the specific daemon (e.g., vsftpd, OpenSSH, ProFTPD) via 'rpm -q <package>' or 'dpkg -l <package>' or check service binary version with '<daemon> -v' or 'sshd -v'. Compare against any vendor advisories for version ranges.
    Affected if The installed version is older than the patched version (if known) or is unpatched
  3. Inspect firmware directory permissions
    Locate firmware locations (common paths: /boot, /lib/firmware, /usr/share/<app>/firmware, or vendor-specific paths like /opt/<product>/firmware). Check permissions with 'ls -la <firmware_dir>' - verify files are NOT world-readable or accessible by low-privilege service users.
    Affected if Firmware files are readable by non-privileged users or the service account running FTP/SFTP without explicit authorization
  4. Inspect certificate and private key permissions
    Find certificate/key files (paths like /etc/ssl, /etc/pki, /opt/<app>/certs, or application-specific directories). Check ownership and permissions with 'ls -la <cert_dir>' - ensure private keys (files ending in .key or private) are not readable by group/other.
    Affected if Certificate or private key files are readable by the FTP/SFTP service user or by world/group
  5. Verify service user privilege separation
    Check the service configuration: for vsftpd examine /etc/vsftpd.conf for 'anon_root' and user privileges. For OpenSSH/sftpd check /etc/ssh/sshd_config for 'ChrootDirectory' and 'ForceCommand' settings. Ensure services run with minimal privileges and cannot access outside their chroot/jail.
    Affected if Service runs as root or with elevated privileges, or lacks proper chroot/privilege separation configuration

A user is affected if FTP or SFTP services are running and can be accessed by low-privileged remote attackers who can read firmware files, certificates, or private keys due to insufficient permission controls on these sensitive resources.

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

Review and fix permission handling code in runtime services (FTP/SFTP) to enforce proper access controls on sensitive resources like firmware and certificates. Implement principle of least privilege for all service operations.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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