{
"id": 9912459314,
"name": "0x21C7",
"description": "This is a 16-bit hexadecimal number translating to 8647 in decimal, consisting of 86 (stop, remove) and 47 (ᵗʰ US president, referring to Trump's second term). Originally on Azure/Aqua-blue checkered background, it appeared like water ripples on the freshly coated Lincoln Memorial Reflecting Pool. This hurt legibility, so Aqua was later recolored to bluish green for uniform brightness and to refer to Trump's pool resurfacing corruption scandal that resulted in algae coloring the pool green..",
"links": {
"website": [
"https://en.wikipedia.org/wiki/86_47",
"https://en.wikipedia.org/wiki/Lincoln_Memorial_Reflecting_Pool#2026_renovations"
]
},
"path": {
"15-48": [
[
158,
75
],
[
159,
75
],
[
159,
74
],
[
195,
74
],
[
195,
75
],
[
196,
75
],
[
196,
83
],
[
195,
83
],
[
195,
82
],
[
192,
82
],
[
192,
82
],
[
192,
83
],
[
186,
83
],
[
185,
83
],
[
185,
84
],
[
181,
84
],
[
181,
83
],
[
170,
83
],
[
170,
84
],
[
159,
84
],
[
159,
83
],
[
158,
83
],
[
158,
83
],
[
158,
75
]
]
},
"center": {
"15-48": [
163,
79
]
}
}
redjard
Former account: @Redjard@lemmy.dbzer0.com
Keyoxide: aspe:keyoxide.org:KI5WYVI3WGWSIGMOKOOOGF4JAE (think PGP key)
- 1 post
- 1 comment
Joined 3 years ago
Cake day: August 6th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.


Just fyi, the nginx vulnerabilities are all impractical to use. The bugs are use after free, which will almost definitely lead to a crash in the worker process and have them be restarted.
That itself would make it about as bad as the mp-tcp style expoits lately, but it’s even weaker. If you could keep trying, you could strap an llm into figuring out a specific machine and after tons of compute eventually get out data or take controll of the nginx-owned process.
But, the restarts should restart that process, so I don’t see almost any risk unless you have address randomization disabled, which would be highly unusual.
Unless I am missing something here, I see a bigger risk with an unmentioned loop that was also fixed in nginx. That one lets you make a worker thread hang, so you can disable a server until someone notices and restarts nginx. That ddos affects servers with tls1.3 support.
Also their “2root” is just a completely unrelated kernel bug they bundled for marketing, which is pissing me off tbh. All of this “security research” for marketing is the worst possible contradictory incentive. You wanna release as poorly as possible to maximize fear mongering.
They didn’t even release the bug, for all we know is as convoluted to use as the mp-tcp stuff and affects basically noone. Not that the nginx side is exploitable.