Been fighting a nightmare bug in busybox awk. It all started yesterday when I was looking into fixing CVE-2023-42364 and CVE-2023-42365. I found out that git master did not trigger the POC. With git bisect I found the commit which coincidentally fixes the issue. Cherry-pick. all good.
Today I got a report that busybox awk was broken. The "fix" introduces a nasty regression. Some more research revealed that the commit is very questionable.
So now I'm reverting it, and we are back to start.
Natanael Copa /
npub1wz…e9235
2024-05-21 13:55:56
Author Public Key
npub1wzzd3lvf084kth7jtszr3aqsxqwgs76t6wsfgqvl8w7u2auw26mske9235Published at
2024-05-21 13:55:56Event JSON
{
"id": "158cc238d02d6b8ca1a83315f1b5e34ffd7bf6a3380cbf95951a4e7598929f1b",
"pubkey": "7084d8fd8979eb65dfd25c0438f410301c887b4bd3a094019f3bbdc5778e56b7",
"created_at": 1716299756,
"kind": 1,
"tags": [
[
"proxy",
"https://fosstodon.org/users/ncopa/statuses/112479420845913893",
"activitypub"
]
],
"content": "Been fighting a nightmare bug in busybox awk. It all started yesterday when I was looking into fixing CVE-2023-42364 and CVE-2023-42365. I found out that git master did not trigger the POC. With git bisect I found the commit which coincidentally fixes the issue. Cherry-pick. all good.\n\nToday I got a report that busybox awk was broken. The \"fix\" introduces a nasty regression. Some more research revealed that the commit is very questionable.\n\nSo now I'm reverting it, and we are back to start.",
"sig": "cef646d327a2148cf10ff0d019e6b125c870a6c508026a2931466d0a443b312698d71ab80c33b42bfbc56f5417c84c735416c4a2c568a432111f3134e30897e7"
}