
Dockerized Apache Solr CTF challenge reproducing CVE-2026-44825 default-credential authentication bypass, with GZCTF deployment config, exploit script, and writeup.
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).
solr / SolrRocks) as-isid:flag) inside Solr and can only be retrieved with administrator privileges.# (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
When registering/modifying this challenge in the CTF platform (GZCTF) admin page, the following values must be set correctly.
| Setting item | Value | Reason |
|---|---|---|
| Container Image | chal/baek10023:v1 (or the tag of the image you built) | Use the image built from this repo as-is |
| Expose Port | 8983 | Solr 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 Template | WINS{[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 Limit | 256 (MB) | Match mem_limit: 256m in docker-compose.yml |
| CPU Count | 0.5, or 1 if the platform does not support decimals | Match cpus: "0.5" in docker-compose.yml as closely as possible. If the GZCTF UI only accepts integers, set it to 1 |
| Container Type | Dynamic 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.
docker-compose.yml and do not touch the internal port (8983).FLAG (local) or GZCTF_FLAG (competition platform) environment variable.
Do not hardcode the actual flag in the source/image.healthy state before connecting.exploit/ and WRITEUP.md, which reveal the solution
method as-is. Be sure to check the repo's visibility (Public/Private).