https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 19:41:52 +0000 https://vulnerability.circl.lu/vuln/ghsa-f67j-2jqw-jpq7 <p><strong>Affected:</strong> npm: @angular/platform-server</p> <p>A Denial of Service (DoS) vulnerability exists in `@angular/platform-server`&#39;s DOM emulation parser (`domino`). When processing untrusted user input containing an incomplete DOCTYPE declaration ending with whitespace before EOF (such as `&lt;!DOCTYPE html `), the HTML parser enters an infinite synchronous loop, pegging CPU utilization at 100% and completely freezing the Node.js server process.</p> <p>### Technical Description In Angular Server-Side Rendering (SSR), `@angular/platform-server` uses `domino` to parse and sanitize HTML bound through template bindings (such as `[innerHTML]`) or manipulated via DOM APIs.</p> <p>In Domino&#39;s HTML parser (`lib/HTMLParser.js`), tokenizer states that specify fixed lookahead—such as `after_doctype_name_state` (`lookahead = 6`)—rely on the state handler function to explicitly advance the character index pointer (`nextchar`). While branches for whitespace, `&gt;`, and keyword matching advance `nextchar`, the EOF branch (`case -1: // EOF`) emitted doctype and EOF tokens without advancing `nextchar` or transitioning out of the state:</p> <p>```javascript case -1: // EOF forcequirks(); emitDoctype(); emitEOF(); break; ```</p> <p>Because `nextchar` remained unchanged pointing to the EOF marker character (`\uFFFF`), the scanner loop (`while (nextchar &lt; numchars)`) repeatedly re-invoked `after_doctype_name_state` with `codepoint = EOF` indefinitely. In Node.js&#39;s single-threaded runtime, this synchronous loop starves the event loop entirely.</p> <p>### Impact &amp; Reachabilit…</p> <p><strong>Affected:</strong> npm: @angular/platform-server</p> <p>A Denial of Service (DoS) vulnerability exists in `@angular/platform-server`&#39;s DOM emulation parser (`domino`). When processing untrusted user input containing an incomplete DOCTYPE declaration ending with whitespace before EOF (such as `&lt;!DOCTYPE html `), the HTML parser enters an infinite synchronous loop, pegging CPU utilization at 100% and completely freezing the Node.js server process.</p> <p>### Technical Description In Angular Server-Side Rendering (SSR), `@angular/platform-server` uses `domino` to parse and sanitize HTML bound through template bindings (such as `[innerHTML]`) or manipulated via DOM APIs.</p> <p>In Domino&#39;s HTML parser (`lib/HTMLParser.js`), tokenizer states that specify fixed lookahead—such as `after_doctype_name_state` (`lookahead = 6`)—rely on the state handler function to explicitly advance the character index pointer (`nextchar`). While branches for whitespace, `&gt;`, and keyword matching advance `nextchar`, the EOF branch (`case -1: // EOF`) emitted doctype and EOF tokens without advancing `nextchar` or transitioning out of the state:</p> <p>```javascript case -1: // EOF forcequirks(); emitDoctype(); emitEOF(); break; ```</p> <p>Because `nextchar` remained unchanged pointing to the EOF marker character (`\uFFFF`), the scanner loop (`while (nextchar &lt; numchars)`) repeatedly re-invoked `after_doctype_name_state` with `codepoint = EOF` indefinitely. In Node.js&#39;s single-threaded runtime, this synchronous loop starves the event loop entirely.</p> <p>### Impact &amp; Reachabilit…</p> https://vulnerability.circl.lu/vuln/ghsa-f67j-2jqw-jpq7