• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

nats-io / nats-server / 20052263983 / 1
85%
main: 85%

Build:
DEFAULT BRANCH: main
Ran 09 Dec 2025 05:53AM UTC
Files 61
Run time 4s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

08 Dec 2025 11:02PM UTC coverage: 84.691% (-0.06%) from 84.751%
20052263983.1

push

github

web-flow
[FIXED] Websocket: limit buffer size during decompression of a frame (#7625)

When the server would decompress a compressed websocket frame, it would
not limit the resulting size of the uncompressed buffer. Once
uncompressed the maximum payload size would still be used to reject
messages that are too big, but the server would have already
uncompressed a possibly very big buffer (if the frame contained highly
compressed data).

This PR limits the number of bytes that are being decompressed using the
maximum payload size as a limit.

Credit goes to:
Pavel Kohout, Aisle Research (www.aisle.com) for reporting the issue and
providing a path.

The propose patched as been updated a bit (need to use atomic to use the
connection's max payload value) and some tweaks around the use of the
`io.LimitedReader`.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>

74061 of 87449 relevant lines covered (84.69%)

360453.84 hits per line

Source Files on job 20052263983.1
  • Tree
  • List 61
  • Changed 21
  • Source Changed 3
  • Coverage Changed 21
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 20052263983
  • 714d4648 on github
  • Prev Job for on main (#20017030728.1)
  • Next Job for on main (#20087658921.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc