Vulnerabilities

 2 via 2 paths

Dependencies

 88

Source

 GitHub

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 1
  • 1
Status
  • 2
  • 0
  • 0

high severity
new

Server-side Request Forgery (SSRF)

  • Vulnerable module: @angular/platform-server
  • Introduced through: @angular/platform-server@21.2.8

Detailed paths

  • Introduced through: angularexampleapp@ismaestro/angular6-example-app › @angular/platform-server@21.2.8
    Remediation: Upgrade to @angular/platform-server@21.2.9.

Overview

@angular/platform-server is an Angular - library for using Angular in Node.js

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in the URL parsing during Server-Side Rendering (SSR). An attacker can cause the server to make arbitrary HTTP requests to attacker-controlled domains by sending specially crafted requests with protocol-relative or backslash-prefixed URLs. This can result in exposure of internal APIs or metadata services if the server performs HTTP requests using relative URLs or constructs URLs based on the manipulated origin.

Note:

Affected APIs (used with Angular SSR):

  • renderModule
  • renderApplication
  • CommonEngine

Workaround

This vulnerability can be mitigated by implementing middleware to sanitize incoming request URLs, ensuring they start with a single forward slash and removing any leading backslashes or multiple slashes.

Remediation

Upgrade @angular/platform-server to version 19.2.21, 20.3.19, 21.2.9, 22.0.0-next.8 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity
new

Open Redirect

  • Vulnerable module: @angular/ssr
  • Introduced through: @angular/ssr@21.2.7

Detailed paths

  • Introduced through: angularexampleapp@ismaestro/angular6-example-app › @angular/ssr@21.2.7
    Remediation: Upgrade to @angular/ssr@21.2.9.

Overview

@angular/ssr is a the Angular server side rendering utilities.

Affected versions of this package are vulnerable to Open Redirect via improper handling of the X-Forwarded-Prefix header. An attacker can manipulate internal redirects or server-side requests by injecting encoded path traversal sequences, which are decoded and used by the application logic. This can result in unintended redirects or requests to internal or external endpoints.

Note: This is only exploitable if the application is configured to trust proxy headers and is deployed behind a proxy that forwards the X-Forwarded-Prefix header without prior sanitization.

Remediation

Upgrade @angular/ssr to version 19.2.25, 20.3.25, 21.2.9, 22.0.0-next.7 or higher.

References

Open Redirect vulnerability report