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
CVE-2026-44825_CTF — Dockerized Apache Solr CTF challenge reproducing CVE-2026-44825 default-credential authentication bypass, with GZCTF deployment config, exploit script, and writeup. | Kitploit
Tools/GitHubGitHub/q0524/cve-2026-44825_ctf
Container SecurityVulnerability AnalysisExploitationWeb Application ExploitationCTFPenetration TestingLearning & EducationLabs & Practice
GitHubq0524/cve-2026-44825_ctf

CVE-2026-44825_CTF

Dockerized Apache Solr CTF challenge reproducing CVE-2026-44825 default-credential authentication bypass, with GZCTF deployment config, exploit script, and writeup.

1 month agoNot yet reviewed
Share
View Repository

CVE-2026-44825 — Apache Solr Default Credentials Vulnerability

1. What Is This Repository

This repository reproduces, as a Docker container, the vulnerable Apache Solr server that participants must attack to find the flag value in the "CVE-2026-44825" challenge on the CTF page (GZCTF).

  • Vulnerability: Apache Solr's default authentication setup tool sets publicly known default credentials (solr / SolrRocks) as-is
  • Impact: Logging in with these default credentials grants administrator privileges over the entire cluster
  • Affected versions: Apache Solr 9.4.0 ~ 9.10.1, 10.0.0
  • The flag is stored as a document (id:flag) inside Solr and can only be retrieved with administrator privileges.
  • For a detailed walkthrough, see WRITEUP.md; for the automated exploit script, see exploit/exploit.py.

2. Execution Order After git clone

# (1) 레포 받기
git clone https://github.com/q0524/CVE-2026-44825_CTF.git
cd CVE-2026-44825_CTF
# (2) 컨테이너 빌드 + 실행
#     - 통합 서버 배포 시: 실제 flag 를 환경변수로 주입
#     - 로컬 테스트 시: FLAG 를 생략하면 placeholder 값 사용
FLAG='WINS{real_flag_here}' docker compose up -d --build
# (3) 정상 구동 확인
docker compose ps
curl -I http://localhost:10023/solr/        # 401 이 나오면 정상 (인증 필요 상태)
# (4) 풀이 스크립트로 flag 획득 (참가자 관점 검증)
pip install requests
python3 exploit/exploit.py http://localhost:10023
# (5) 종료 / 재검증 (클린 환경 재현 확인)
docker compose down
docker compose up -d --build

3. Configuration values when registering the challenge in GZCTF

When registering/modifying this challenge in the CTF platform (GZCTF) admin page, the following values must be set correctly.

Setting itemValueReason
Container Imagechal/baek10023:v1 (or the tag of the image you built)Use the image built from this repo as-is
Expose Port8983Solr comes up on port 8983 inside the container (EXPOSE 8983 in the Dockerfile). If you leave the default template value (8080), GZCTF will connect to the wrong port, causing ERR_CONNECTION_REFUSED / ERR_EMPTY_RESPONSE.
Flag TemplateWINS{[GUID]}This must be set. If left blank, GZCTF generates the flag in its own default format, breaking the WINS{...} format required by the challenge.
Memory Limit256 (MB)Match mem_limit: 256m in docker-compose.yml
CPU Count0.5, or 1 if the platform does not support decimalsMatch cpus: "0.5" in docker-compose.yml as closely as possible. If the GZCTF UI only accepts integers, set it to 1
Container TypeDynamic Container (creates a separate instance per team)Since each participant must receive a different flag, set it as a dynamic container rather than a static/shared container

If any of these values is left blank or kept at the template default, the container may build successfully but participants will be unable to connect or the flag format will be wrong. After registering the challenge, launch an instance yourself with "Start Challenge" and verify port connectivity and the flag format.

4. Notes

  • Port: Fixed to external 10023 / internal 8983. If you want to use a different port, change only the port mapping in docker-compose.yml and do not touch the internal port (8983).
  • Memory: Limited to 256m, and the Solr JVM heap is also set to 128m. Raising this value may exceed the per-container memory limit of the integration server.
  • Flag injection: The flag is injected only via the FLAG (local) or GZCTF_FLAG (competition platform) environment variable. Do not hardcode the actual flag in the source/image.
  • Initial startup time: It takes about 30–60 seconds for Solr to come up, create the core, and index the flag. Wait until the container reaches the healthy state before connecting.
  • No external network dependency: External packages are fetched only at build time, and at runtime it operates without an internet connection.
  • x86/ARM: Since it is based on the official Solr image, it does not depend on architecture-specific binaries.
  • Flag exposure warning: This repo includes exploit/ and WRITEUP.md, which reveal the solution method as-is. Be sure to check the repo's visibility (Public/Private).
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.

    837
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    536
  • 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.

    424
  • 4

    redforge

    cybersecurity91/redforge

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

    355
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    294
  • 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.

    276

Explore all tools

Browse our collection of tools

View all tools →