Unrestricted File UploadWeakness · CWE-434

CVE-2025-24505

HIGH · 8.8 CVSS v4.0 Published 2025-01-30

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

90/100

Remediation priority · Urgent

Zero-click

Official description

NVD · unedited

This vulnerability allows a high-privileged authenticated PAM user to achieve remote command execution on the affected PAM system by uploading a specially crafted upgrade file.

Technical summary

dbcve analysis · moderate confidence

A file upload vulnerability in a PAM (Privileged Access Management) system allows high-privileged authenticated users to achieve remote command execution by uploading specially crafted upgrade files. The upgrade mechanism insufficiently validates the uploaded file, permitting arbitrary code execution in the context of the PAM system.

MitigationRestrict upgrade file uploads to only verified, signed packages from trusted sources, implement strict file type validation and content inspection, and run upgrade processing in an isolated sandbox environment.

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

CVSS breakdown

From the vector

Attack vector: Adjacent
Complexity: High
Privileges: High
Authentication: X
User interaction: None
Scope: X

CVSS:4.0/AV:A/AC:H/AT:N/PR:H/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:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify PAM system in use

Inventory your environment for Privileged Access Management (PAM) software installations. Check for common PAM products by reviewing installed software lists, service processes, or web applications running on typical ports (e.g., 443, 8443). Look for PAM-related service names or process executables.

Affected if A PAM system is present and has an upgrade/upload feature enabled
Locate upgrade or file upload functionality

Examine the PAM system administrative interface for upgrade, patch, or file upload features. Check the web application URL paths for common upgrade endpoints (e.g., /upgrade, /upload, /patch, /update). Review system documentation or UI navigation for 'System Upgrade', 'Software Update', or 'Plugin Upload' sections.

Affected if The upgrade/upload feature exists and is accessible to high-privileged users
Verify high-privileged user access

Review PAM system role definitions and confirm which user roles possess 'Administrator', 'Super Admin', or 'Upgrade' permissions. Check if standard privileged users (non-root, non-owner accounts) can access upgrade or upload features.

Affected if High-privileged authenticated users can access the upgrade/upload functionality
Inspect file validation configuration

Access PAM system configuration files or admin settings related to file uploads. Look for parameters controlling file type validation, signature verification, content inspection, or sandboxing. Common config locations: config.xml, upload.conf, security.json, or admin GUI settings panels.

Affected if File validation is disabled, weak (e.g., only extension-based), or absent in the upgrade configuration
Check for unauthorized upgrade files

Review the PAM system directories where upgrade files are stored or processed. Look for unexpected .zip, .tar, .jar, or executable files in upgrade staging folders, temp directories, or web root. Compare against known legitimate upgrade packages.

Affected if Unexpected or unsigned upgrade files exist in the system or upload directories

You are affected if a PAM system with an upgrade/upload feature is present, high-privileged users can access it, and file validation is weak or absent.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Restrict upgrade file uploads to only verified, signed packages from trusted sources, implement strict file type validation and content inspection, and run upgrade processing in an isolated sandbox environment.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation16.0 h
Testing8.0 h
Review / QA4.0 h

32.0 hours of engineering $5,600

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

support.broadcom.com
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24505 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-24505?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

A high-priority fix

Have this fixed 32 hrs · High

Typical engagement from $5,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-24505 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References