CVE-2025-62427
BaseFortify
Publication date: 2025-10-16
Last updated on: 2025-10-21
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| angular | ssr | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Server-Side Request Forgery (SSRF) flaw in Angular CLI's Server-Side Rendering package (@angular/ssr) before versions 19.2.18, 20.3.6, and 21.0.0-next.8. It occurs because the URL resolution mechanism incorrectly handles incoming request paths that start with double forward slashes (//) or backslashes (\\). The native URL constructor treats such paths as schema-relative URLs, overriding the intended base URL and allowing an attacker to specify an external domain. This tricks the Angular SSR environment into setting the page's virtual location to the attacker's domain, causing any subsequent relative HTTP requests during SSR to be resolved against the attacker's domain, potentially forcing the server to communicate with arbitrary external endpoints.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing an attacker to manipulate the server-side rendering process to make the server send HTTP requests to arbitrary external domains controlled by the attacker. This can lead to unauthorized data exposure, server-side request manipulation, or interaction with malicious endpoints, potentially compromising server integrity, confidentiality, or availability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Angular SSR package (@angular/ssr) to version 19.2.18, 20.3.6, or 21.0.0-next.8 or later, where the issue is fixed. Avoid processing URLs that begin with double forward slashes (//) or backslashes (\) in your server-side rendering logic until the update is applied.