Skip to content
KitploitKITPLOIT
도구블로그
제출
도구블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

··피드·문의·개인정보·© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
pois0nSword — A demonstration of read write using cve-2025-43529 on iOS 26.1 | Kitploit
도구/GitHubGitHub/genericcoding/pois0nsword
Exploit FrameworksiOS SecurityVulnerability AnalysisExploitationReverse EngineeringMobile SecurityPayload DevelopmentBinary Exploitation
GitHubgenericcoding/pois0nsword

pois0nSword

A demonstration of read write using cve-2025-43529 on iOS 26.1

저장소 보기
581525일 전Kitploit 검토 완료

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →
공유
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

pois0nSword

In development, not currently useful for users.

pois0nSword is an iOS project with the goal of eventually enabling user interface customization.

Currently a demonstration of arbitrary webcontent read write using cve-2025-43529 on iOS 26.1. As well as a PAC bypass utilizing CVE-2026-20700. Credits:

GenericCoding - main developer varik - main developer

zeroxjf - fixing webcontent r/w and debugging

  • R/W primatives
  • PAC bypass / offsets
  • GC disabling
  • JitAllowList overwrite
  • Get slide
  • Get correct vtable for web worker
  • Initial work on creating the web worker for dlopen
  • Most iPhone 15 plus offsets for 26.1
  • Patch offsets with slide
  • Get JSC_base address
  • Angle-OOB sandbox escape
도구 다운로드

Most of the code comes from cve-2025-43529 POC by jir4vv1t and the darksword web implementation. (https://github.com/ghh-jb/DarkSword/)

Write-up

For PAC bypass write up see: https://varik.dev/blog/jsc/pois0nsword-native-calls

For arbitrary webcontent r/w see: https://varik.dev/blog/jsc/jsc-exploitation-primitives-part-1

This repo utilizes the Darksword scribble method to obtain read/write64 primatives on iOS 26.1 after bootstrapping addrof and fakeobj primatives, and then disables garbage collection (See WIP branch) with write8 after obtaining the heap and VM addresses.

Regarding the related ANGLE-OOB bug: The way the OOB referenced in @zeroxjf's analysis repo, is related and is used in DarkSword, however it is used after IPC port which is opened using read / write and offsets, and requires the PAC bypass. Hence why @zeroxjf couldn't verify the OOB fully, without a way of transmitting messages between the OOB and an IPC port; the OOB isn't of use to us at all.