<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Denial of Service on Nalar</title>
    <link>https://nalar.dev/tags/denial-of-service/</link>
    <description>Recent content in Denial of Service on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/denial-of-service/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Bound Work Before Processing Untrusted Input</title>
      <link>https://nalar.dev/bound-work-before-processing-untrusted-input/</link>
      <pubDate>Sun, 06 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/bound-work-before-processing-untrusted-input/</guid>
      <description>&lt;p&gt;An input does not need to be malicious code to hurt a service. It only needs to make the service spend far more memory, CPU time, storage, or concurrency than the sender spent creating the request.&lt;/p&gt;&#xA;&lt;p&gt;A parser may accept deeply nested data. A compressed upload may expand far beyond its transfer size. A search endpoint may allow a query that is valid but unusually expensive. If enough work begins before the application applies a limit, a small amount of incoming traffic can consume resources needed by legitimate users.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
