Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

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

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

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
도구/GitHubGitHub/googlesky/cve-2026-131842
ExploitationWeb Application ExploitationSecurity VirtualizationPenetration TestingPapers & ResearchLabs & Practice
GitHubgooglesky/cve-2026-131842

CVE-2026-131842

Proof-of-concept lab for CVE-2026-131842: Poppler pdfdetach path traversal via crafted embedded file names, with vulnerable/fixed containers and exploit scripts.

저장소 보기웹사이트
1일 전아직 검토되지 않음

인기

모두 보기 →

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

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 궁극의 OSINT 툴킷: 조사 그래프, 신뢰도 점수 산정, 별칭 패밀리, 지도, 타임라인 및 보고서. 49개 모듈, 400개 이상 사이트, API 키 불필요.

    938
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # GhostLock 원탭 실행 앱 (CVE-2026-43499)

    556
  • 3

    redforge

    cybersecurity91/redforge

    브라우저 측 레드 팀 툴킷으로, 정찰, 페이로드 생성, 자격 증명 공격, 암호화, 인코딩 및 참여 보고를 위한 102개의 오프라인 도구를 제공합니다.

    352
  • 4

    ARTEX

    baarai/artex

    LLM 멀티 에이전트 자율 침투 테스트 플랫폼으로, 플래너/워커 에이전트, 자산 및 탐색 그래프, MITM 트래픽 기록, 취약점 재테스트 기능을 제공합니다.

    343
  • 5

    looking-glass

    anonghosty/looking-glass

    Shadowserver 보고서를 MongoDB로 수집하고 이를 대화형 지도, 분석, 발견 사항, 권고 및 경영진 대시보드로 재생하는 CSIRT 플랫폼입니다.

    336
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AI 네이티브 사이버보안을 위한 행동 체계—의도가 통제된 실행이 되고, 증거가 운영 메모리가 되며, 모든 운영이 다음 운영을 개선하는 곳.

    291

모든 도구 탐색

도구 컬렉션을 둘러보세요

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

CVE-2026-131842 — Poppler pdfdetach: path traversal via embedded file names (string-prefix containment bypass)

License: MIT Research status: validated

CVECVE-2026-131842
ComponentPoppler utils/pdfdetach.cc — -saveall / -savefile extraction
Affectedpdfdetach 24.03.0 through 26.11.0
Fixed inno upstream fix yet (work item 1826 OPEN); this lab's fixed side carries a documented synthetic component-aware containment patch
CWECWE-22 (Improper Limitation of a Pathname to a Restricted Directory)
ImpactArbitrary file create/overwrite with the privileges of whoever runs pdfdetach — any document pipeline that detaches embedded files from untrusted PDFs into a quarantine directory (pdfdetach -saveall -o <dir>) can be made to write outside that directory (config, cron, source trees, SSH keys — anything writable)
VectorFile format — a crafted PDF whose embedded-file name escapes the output directory
Triggerone upload whose embedded file name is ../<base-suffix>/… (sibling-prefix bypass) or passes through a symlink inside the output directory

Since 24.03.0 the output directory is "protected" by a string-prefix containment check:

// utils/pdfdetach.cc @ poppler-26.11.0 (~L220)
std::filesystem::path filePath = basePath;
filePath = filePath.append(currentFileName).lexically_normal();

if (!filePath.generic_string().starts_with(basePath.generic_string())) {
    error(errIO, -1, "Preventing directory traversal");
    return 3;
}
embFile->save(filePath.generic_string());

starts_with on the normalized string is not containment. With base /work/quarantine, an embedded name ../quarantine-staging/pwned.txt normalizes to /work/quarantine-staging/pwned.txt — outside the base, yet a string prefix of it — so the guard passes and save() writes the file. A symlink inside the output directory defeats the check the same way: the lexical path stays "inside" while fopen() follows the link. This laboratory demonstrates both forms deterministically.


1. Root cause

lexically_normal() + generic_string().starts_with(base) checks characters, not path components. Two consequences:

  1. Sibling-prefix escape — any normalized path that shares the base string as a prefix passes, including paths in sibling directories (../quarantine-staging/…) or, with a trailing-slash-less base, sibling entries at every level.
  2. Symlink following — the check never resolves symlinks, so an existing symlink inside the output directory redirects the write anywhere on the filesystem.

The older 2023-era fix (commit d8e7a8a9, "Fix directory traversal in pdfdetach") survived into 24.03+ in this weakened form; upstream work item 1826 tracks the bypass and is still open — there is no vendor fix to differential against yet.

2. Reproduction environment

serviceimagerole
pdf-vulncve-2026-131842:vulnpdfdetach built from upstream tag poppler-26.11.0 as-is
pdf-fixedcve-2026-131842:fixedsame tree + synthetic component-aware containment patch (sha256 in evidence/versions.txt)
poccve-2026-131842-poc:localstdlib-only Python driver that crafts the PDFs

The pipeline service models a real product flow: POST /detach accepts a PDF, runs pdfdetach -saveall -o /work/quarantine <pdf> as a child process, and reports every file created outside the quarantine directory. Two lab preconditions (identical on both sides) make the vectors deterministic and are documented as such: a sibling directory /work/quarantine-staging (writes need an existing parent) and a symlink /work/quarantine/link-escape → /work/escape-zone — both plausible in any pipeline that accumulates staging dirs and symlinks.

3. Running the environment

./run-lab.sh build     # builds poppler 26.11.0 twice (with/without the patch)
./run-lab.sh up        # cve131842lab network: pdf-vuln, pdf-fixed
./run-lab.sh sweep     # check / exploit / probe / mitigation on both sides
./run-lab.sh down

4. The PoC

A standalone full-chain exploit script ships at exploit/exploit.py (python3 exploit/exploit.py --host=<target>; exit 1 on confirmed exploitation, 0 on a safe target).

poc/poc.py (stdlib only — it writes the minimal PDF bytes itself):

  • check — benign embedded name (stays inside), then the sibling-prefix bypass; exit 1 when a file lands outside the quarantine, 0 when containment holds, 3 no worker, 2 unreachable.
  • exploit — narrated chain with the escaped file path and its marker content as proof.
  • probe — matrix: sibling-prefix, symlink, benign control, plain .. control.
  • mitigation — the synthetic patch side; the symlink residual is stated.

5. Expected results

casepdf-vuln (26.11.0)pdf-fixed (synthetic patch)
benign doc.txtsaved inside quarantine, exit 0exit 0
../quarantine-staging/pwned-prefix.txtwritten outside, exit 0rejected "Preventing directory traversal", exit 3
link-escape/pwned-sym.txtwritten through symlink, exit 0still written (residual)
../pwned-direct.txt (control)blocked, exit 3blocked, exit 3

Captured runs: evidence/check-*-run.txt, evidence/exploit-*-run.txt, evidence/probe-*-run.txt, evidence/mitigation-*-run.txt, evidence/versions.txt, evidence/0day-sweep.txt.

6. Environment preconditions

  • Podman (or Docker) with network-creation rights; containers bounded on the isolated cve131842lab network.
  • Outbound HTTPS at image build (gitlab.freedesktop.org git clone; debian mirrors).
  • Build needs cmake ≥ 3.28 (debian:trixie build stage); runtime needs freetype/fontconfig/harfbuzz shared libraries.

7. Additional findings (0-day sweep on the fixed line)

The probe matrix on the patched build (evidence/0day-sweep.txt) shows the synthetic component-aware check closes the sibling-prefix bypass but cannot close the symlink form — lexical containment never resolves links. The symlink variant remains exploitable on every release through 26.11.0 and on this lab's fixed side; it needs a std::filesystem::weakly_canonical-based check (or extraction into a directory the process cannot traverse out of, e.g. a per-job mount namespace). That residual is documented upstream in work item 1826. Deployment mitigations until a vendor fix: reject embedded names containing .. components before invoking pdfdetach, and run detachment in a container without write access outside the quarantine.

8. Repository layout

README.md             this write-up
run-lab.sh            environment driver (build / up / sweep / down)
Makefile              convenience targets
exploit/exploit.py    standalone full-chain exploit
poc/poc.py            the PoC (check / exploit / probe / mitigation)
poc/Dockerfile        runner image (python:3.12-alpine)
lab/lab.Dockerfile    multi-stage build (poppler 26.11.0 with/without patch)
lab/patches/fix-prefix-containment.patch   the synthetic fixed-side patch
lab/service.py        the document-pipeline service (POST /detach)
evidence/             captured runs of every mode on both sides
TRACKING.md           excluded (working record)

9. References

도구 다운로드