3 Followers
19 Following
6 Posts
My sheet is a joke

@BednarTildeOne Last week, I tried rewriting the PoC using only your writeup as a reference. Although I successfully triggered code execution, SystemUI kept crashing. After digging into your original source code, I finally found the 'treasure' that specific fix this.
I’m also the one who submitted the PR to `ThisSeemsWrong`; I hadn't realized at the time that the issue was due to a different writeTypedObject implementation.

I really enjoy your writeups, and personally I find digging into the PoCs even more fun.
Thanks for the great work!

@BednarTildeOne By the way,the cleanup skills are truly impressive.
@BednarTildeOne Interesting,thanks for your time.

@BednarTildeOne

Hello Michal,

I recently read your excellent write-up, ResourcePoison

I observed what seems like an unusual construction pattern in LoadedApk.java. Specifically, the Shellcode class appears to be constructed twice in the following locations within the file:

- https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/app/LoadedApk.java;drc=50f34b45baed2ec3a256f1c65df4865d72452768;l=376

- https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/core/java/android/app/LoadedApk.java;drc=50f34b45baed2ec3a256f1c65df4865d72452768;l=393

I am wondering if this double construction is a result of the Proof-of-Concept (PoC) leveraging an unusual execution flow, or if this behavior is an intentional design (or perhaps an unintentional error) within the Android Open Source Project (AOSP) code itself.

@BednarTildeOne hello Michal,previously I've written some notes (in Chinese) on CVE-2023-20944 which is really a wonderful job!! I learned from it so much (and your other reports),I hope my blog did not cause any offense

https://konata.github.io/posts/creator-mismatch/

https://konata.github.io/posts/creator-mismatch-cont/

Creator Mismatch

Prologue

开元米粉实力代购