Homepage

@angular/platform-server@10.0.0-next.0.with-local-changes

Angular - library for using Angular in Node.js

  • latest version

    22.1.1

  • latest non vulnerable version

    22.2.0-next.1

  • first published

    10 years ago

  • latest version published

    2 days ago

  • licenses detected

  • View platform-server package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @angular/platform-server package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Cross-site Scripting (XSS)

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

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the bundled domino DOM serializer, which does not escape text nodes inside the fallback raw-content elements <iframe>, <noembed>, <noframes>, and <noscript> during SSR serialization. An attacker can execute same-origin JavaScript against any visitor to a server-rendered page by supplying data that is bound inside one of those elements and contains a closing tag that ends the element early and opens a script context. This requires the SSR application to bind user-controlled values inside one of those fallback raw-content elements, and the vulnerable serialization path is reached with critical CSS inlining enabled, which is the default.

    How to fix Cross-site Scripting (XSS)?

    Upgrade @angular/platform-server to version 20.3.27, 21.2.19, 22.0.7 or higher.

    <20.3.27>=21.0.0-next.0 <21.2.19>=22.0.0-next.0 <22.0.7
    • H
    Server-side Request Forgery (SSRF)

    @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) via a parser differential between the strict WHATWG URL parser used for allowlist validation and the lenient Domino URL parser used to initialize the server emulated DOM. An attacker can redirect server-side outgoing requests to arbitrary external endpoints and potentially inject malicious content into the rendered HTML by sending specially crafted HTTP requests with malformed Host headers or absolute-form request URIs.

    Note: This is only exploitable if the application is configured for server-side rendering, reconstructs request URLs from raw client inputs, performs outbound backend API requests using relative paths, and has the allowedHosts option enabled.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade @angular/platform-server to version 19.2.23, 20.3.22, 21.2.15, 22.0.0-rc.2 or higher.

    <19.2.23>=20.0.0-next.0 <20.3.22>=21.0.0-next.0 <21.2.15>=22.0.0-next.0 <22.0.0-rc.2
    • H
    Server-side Request Forgery (SSRF)

    @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) through the processing of absolute-form URLs in the server-side rendering engine. An attacker can redirect internal HTTP requests to an attacker-controlled server by supplying a crafted request URL, potentially exposing sensitive internal APIs or metadata services.

    How to fix Server-side Request Forgery (SSRF)?

    Upgrade @angular/platform-server to version 19.2.22, 20.3.21, 21.2.13, 22.0.0-next.12 or higher.

    <19.2.22>=20.0.0-next.0 <20.3.21>=21.0.0-next.0 <21.2.13>=22.0.0-next.0 <22.0.0-next.12
    • M
    Server-side Request Forgery (SSRF)

    @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

    How to fix Server-side Request Forgery (SSRF)?

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

    <19.2.21>=20.0.0-next.0 <20.3.19>=21.0.0-next.0 <21.2.9>=22.0.0-next.0 <22.0.0-next.8
    Go back to all versions of this package