# CVE-2025-24503: Auth bypass in Symantec Privileged Access Management

> Attackers can hijack PAM user sessions by tricking users into clicking crafted links, leading to account takeover.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jan 2025
- **Updated:** 5 Feb 2025
- **Also known as:** GHSA-j634-qrvx-mfvr

## What is CVE-2025-24503?

CVE-2025-24503 is a critical authentication bypass vulnerability in Broadcom Symantec Privileged Access Management, published on 30 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A malicious actor can fix the session of a PAM user by tricking the user to click on a specially crafted link to the PAM server.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2025-24503?


## How do I fix CVE-2025-24503?

No fix has been published for CVE-2025-24503 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24503 being exploited?

There is no known exploitation of CVE-2025-24503 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24503 and fix it if it is affected.

What it is: CVE-2025-24503 is a critical authentication bypass vulnerability in Broadcom Symantec Privileged Access Management, published on 30 Jan 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-24503 in the wild and no public exploit code.

Affected product: Broadcom Symantec Privileged Access Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24503/ (Markdown: https://insights.sbomify.com/CVE-2025-24503/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24503
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24503
- OSV: https://osv.dev/vulnerability/CVE-2025-24503

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24503/
Summaries are generated and may contain mistakes; the official description above is the record.