Normally LFI itself === RCE
Clearly both @TheHackersNews and the author of this "exploit" are COMPETELY IGNORANT of both binary and web security to publish such an absurd post
Now any script kiddy can come up with a ridiculous assumption using AI and put on a show. how pathetic
ASLR bypasses for those are pointless. There are no real Nginx instances vulnerable because that configuration pattern never exists.
Let alone “chaining LFI”; if you can read files on the host you’ve already won. Cut the FUD for no reason.
@calif_io This CVE allows for controlled overflow lengths, since Nginx is forked, one can precisely determine the ASLR offset by sending a maximum of 4.5 * 256 requests.
The fact that you were UNABLE to discover a vulnerability capable of bypassing ASLR does not mean that others cannot.
Besides, if an attacker can already reach eBPF, the real target is usually the verifier (to help):
Break an assumption (with a seprate bug or CFH) then use maps to easily get kernel arbitrary R/W and PC control.
JIT spray is the long way around for eBPF. PLZ play it in cBPF.
Baffling BH US 26 talk:
The threat model looks absolutely absurd as bpf_jit_harden=2 already has an decent bypass https://t.co/rCnIQMj23I
Also BPF_PROBE_MEM32 is on the eBPF path so normally it needs root privilege (CAP_BPF)
How did this considered as a "breakthrough"?
Baffling BH US 26 talk:
The threat model looks absolutely absurd as bpf_jit_harden=2 already has an decent bypass https://t.co/rCnIQMj23I
Also BPF_PROBE_MEM32 is on the eBPF path so normally it needs root privilege (CAP_BPF)
How did this considered as a "breakthrough"?
hotcrp arb file read exploit:
① Register a submission
② Upload any file, view it
③ Add `?docid=2` (change 2 to any number, it's a sequence number start from 2)
And you will be able to read *every* submisson pdf, including others and history version
The bug was patched at v3.2
hotcrp arb file read exploit:
① Register a submission
② Upload any file, view it
③ Add `?docid=2` (change 2 to any number, it's a sequence number start from 2)
And you will be able to read *every* submisson pdf, including others and history version
The bug was patched at v3.2