CVE-2025-24868
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 · uneditedThe User Account and Authentication service (UAA) for SAP HANA extended application services, advanced model (SAP HANA XS advanced model) allows an unauthenticated attacker to craft a malicious link, that, when clicked by a victim, redirects the browser to a malicious site due to insufficient redirect URL validation. On successful exploitation attacker can cause limited impact on confidentiality, integrity, and availability of the system.
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 · high confidenceThis is an open redirect vulnerability in SAP HANA XS advanced model's User Account and Authentication (UAA) service. An unauthenticated attacker can craft malicious links containing arbitrary redirect URLs that the vulnerable application will accept due to insufficient validation. When victims click these links, they are redirected to attacker-controlled websites, enabling phishing attacks.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP HANA XS advanced UAA service is in useIdentify if your environment runs SAP HANA with XS advanced components by checking for UAA-related processes, services, or endpoints (typically on ports 30030, 30031, or custom UAA ports). Query your system inventory or running services for 'xsuaa', 'uaa', or 'User Account and Authentication' references.Affected if The system runs SAP HANA XS advanced with an exposed UAA service.
-
Locate UAA redirect URL configurationAccess the UAA service configuration files (commonly in xs-security.json, manifest.yml, or via xs get-authentication). Look for settings related to 'redirectUri', 'logoutRedirect', 'loginURL', or 'callback' parameters.Affected if Redirect URL configuration exists and allows external/untrusted domains.
-
Inspect redirect URL validation rulesReview the UAA security configuration for any allowlist or blocklist entries controlling permitted redirect destinations. Check whether the validation is strict (explicit allowlist of trusted domains) or permissive (accepts any valid URL).Affected if No strict allowlist-based validation is configured, or arbitrary URLs are accepted.
-
Verify unauthenticated redirect parameter handlingTest the UAA login endpoint with a crafted request containing an untrusted redirect parameter (e.g., ?redirect=https://attacker.com). Observe whether the application accepts and follows this redirect without validation.Affected if The UAA service accepts and processes redirect URLs from unauthenticated requests without restricting them to trusted domains.
You are affected if your SAP HANA XS advanced environment exposes a UAA service that accepts arbitrary redirect URLs without strict allowlist validation.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict allowlist-based validation for redirect URLs in the UAA service, ensuring only trusted, pre-approved domains are permitted as redirect destinations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24868 in production — separate from our analysis above.
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.
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.
- 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