It's an experimental feature. It doesn't need a bugfix release because you're not supposed to run it in production, and it's just a DoS, not privilege escalation or something

[–] ysjet@lemmy.world 1 points 8 months ago (1 children)

Experimental features are explicitly defined as requiring CVEs. You are supposed to run them in production, that's why they're available as expiermental features and not on a development branch somewhere. You're just supposed to run them carefully, and examine what they're doing, so they can move out of experiment into mainline.

And that requires knowledge about any vulnerabilities, hence why it's required to assigned CVEs to experimental features.

And I'm not sure why you think a DoS isn't a vulnerability, that's literally one of the most classic CVEs there are. A DoS is much, much more severe than a DDoS.

[–] Bene7rddso@feddit.de 2 points 8 months ago (1 children)

If you do examine what it's doing you will catch this as soon as an attacker exploits it, and can disable it. Also, you should maybe not run the entire production with experimental features enabled. In a stable feature this would absolutely be a CVE, but this is marked experimental because it might not work right or even crash, like here

[–] ysjet@lemmy.world 1 points 8 months ago (1 children)

Correct, I agree you run it with an eye on it (which you should probably do anyway) instead of firing and forgetting (which, to nginx's credit, is typically stable enough you can do that just fine).

That said, nginx treats experimental as something you explicitly run in production- when they announced they added it into experimental they actually specifically say to run it in prod in an A/B setup.

https://www.nginx.com/blog/our-roadmap-quic-http-3-support-nginx/

[–] Bene7rddso@feddit.de 2 points 8 months ago

If you run large‑scale Internet services,

That means if you're large enough that A can pick up the slack if B shits the bed. The only impact would be that you have to use HTTP2