Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/metaredteam/rtx-cve-2023-45779
Android SecurityVulnerability AnalysisExploitationBinary AnalysisSupply Chain SecurityPayload Development
GitHubmetaredteam/rtx-cve-2023-45779

rtx-cve-2023-45779

Proof-of-concept code for Android APEX key reuse vulnerability

View Repository
1098452 years agoReviewed by Kitploit
Share
Website

This repository is provided AS IS to accompany a Meta Red Team X vulnerability disclosure. It is not an official Meta project and will not be supported like one.

A set of scripts and artifacts that demonstrate detection and exploitation of Android devices that ship APEXes signed with test keys from AOSP. See our blog post "Missing signs: how several brands forgot to secure a key piece of Android" for full details of the issue.

Files

  • apex-checker/: A set of Bash scripts to save digests of known test keys and check APEXes en masse for signatures from those keys.
  • apex-forger/: Lightweight wrappers around AOSP's apexer and deapexer tools that make it easy to unpack, modify, and repack an APEX. Like apktool for APEXes.
  • vndk-libt/: Source code for a library we added to a vulnerable APEX to prove we can get code execution. All it does is print the command line of each process that loads it to logcat.

Running the exploit

  1. Clone a recent AOSP source tree (Android 13-ish), envsetup+lunch, and run m apexer deapexer apksigner to build the needed tools.
  2. Update envsetup.sh (the one here, not the one in AOSP) to point $AOSP and $ANDROID_HOST_OUT to the appropriate places.
  3. Obtain any Android device. Update it and enable ADB.
  4. Run adb shell getprop ro.build.version.sdk and adb shell getprop ro.vndk.version.
  5. If the two match, adb pull /system/apex/com.android.vndk.current.apex vndk.apex. If not, adb pull /system_ext/apex/com.android.vndk.v<NN>.apex vndk.apex, where <NN> is ro.vndk.version.
  6. Check if the APEX is vulnerable with apex-checker/check.sh vndk.apex. If the output doesn't start with "OI" (indicating both the outer and the inner signatures are from test keys), this PoC cannot be used (although that does not guarantee the device is secure, as other APEXes may still be vulnerable).
  7. Unpack the APEX with apex-forger/unpack.sh vndk.apex vndk.
  8. Try patching libutils.so in the extracted APEX to load our injected libt.so: git apply --directory=vndk vndk-libt/libutils-v31.patch. If that doesn't work (e.g. different VNDK version), use a hex editor to manually change libc.so to libt.so in the appropriate DT_NEEDED of vndk/payload/lib64/libutils.so.
  9. Build libt.so by running ndk-build inside vndk-libt/. Copy vndk-libt/libs/arm64-v8a/libt.so to vndk/payload/lib64/libt.so.
  10. Extract canned_fs_config from apex_build_info.bp. There's no tool to do this easily: the closest is protoc --decode_raw <vndk/apex_build_info.bp followed by manually unescaping field #3. Place canned_fs_config in vndk/.
  11. Add a line to canned_fs_config, like all the others, for /lib64/libt.so.
  12. Download the test keys for the appropriate VNDK version from here.
  13. Repack the APEX with apex-forger/repack.sh vndk com.android.vndk.v<NN>.{pem,pubkey,pk8,x509.pem}.
  14. Run adb install vndk/forged.apex.
  15. Run adb reboot && adb logcat -s RTXPoC:D.
  16. Observe numerous RTXPoC log messages, each from a process we can execute code in.

Test keys known to apex-checker

The hashes in apex-checker/apk-keys.txt and apex-checker/avb-keys.txt correspond to the outer and inner test keys for the following APEXes. Note that there are also -goog variants of those two lists, which were created by Google after our initial report. Those lists are in general more complete, but we do not know exactly which keys they contain.

  • com.android.appsearch
  • com.android.art
  • com.android.btservices
  • com.android.i18n
  • com.android.mediaprovider
  • com.android.ondevicepersonalization
  • com.android.permission
  • com.android.rkpd
  • com.android.runtime
  • com.android.uwb
  • com.android.virt
  • com.android.vndk.v28
  • com.android.vndk.v29
  • com.android.vndk.v30
  • com.android.vndk.v31
  • com.android.vndk.v32
  • com.android.vndk.v33
  • com.android.wifi
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    510
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    415
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258

Explore all tools

Browse our collection of tools

View all tools →