来源

关联漏洞

描述

🐳 Reproduce and test the CVE-2025-32463 vulnerability in a Docker-based lab environment for security research and practical analysis.

介绍

# 🐧 CVE-2025-32463-lab - Explore Privilege Escalation Risks Simply

## 🔗 Download Now
[![Download CVE-2025-32463-lab](https://img.shields.io/badge/Download%20CVE--2025--32463--lab-blue.svg)](https://github.com/DaadaAyoze/CVE-2025-32463-lab/releases)

## 📋 Overview
This project sets up a Docker environment to reproduce and test the local privilege escalation vulnerability CVE-2025-32463. This means you can experiment with how this vulnerability works in a safe, controlled environment without affecting your actual system.

## 🚀 Getting Started
To get started, you need to download the Docker application if you haven't already. Docker allows you to run applications in containers, which keeps them separate from your main system. 

1. Visit the [Docker website](https://www.docker.com/get-started) and follow the instructions for your operating system to install it.
2. Once Docker is installed, you can proceed to download our application.

## 📥 Download & Install
Visit the [Releases page](https://github.com/DaadaAyoze/CVE-2025-32463-lab/releases) to download the latest version of CVE-2025-32463-lab. 

Once on the Releases page, you will see the available versions listed. Choose the version suitable for your needs and click the download link. The files will typically be compressed for easier downloading (like .zip or .tar.gz). 

### Installation Steps
1. **Extract the files**: Once downloaded, locate the file you downloaded and extract it. You can do this by right-clicking the file and selecting "Extract All" or using your preferred extraction tool.
2. **Open a Terminal**: 
   - On Windows, search for "Command Prompt" or "PowerShell".
   - On Mac, search for "Terminal" in your Applications.
   - On Linux, find your Terminal application in your menu.
3. **Navigate to the folder**: Use the `cd` command to change the directory to the folder where you extracted the files. For example:
   ```
   cd path/to/extracted/folder
   ```
4. **Run the Docker command**: To run the application, you will use a specific command detailed in the README of your extracted folder. It may look something like this:
   ```
   docker-compose up
   ```
   This command will start the application in Docker.

## 🖥️ System Requirements
- **Operating System**: Windows 10, macOS, or any modern Linux distribution.
- **Docker**: Must have the latest stable version of Docker installed.
- **Memory**: At least 4 GB of RAM is recommended for optimal performance.
- **Storage**: 1 GB of free disk space available to run the application. 

## 🚧 Usage Instructions
Once the application is running, you can access the lab environment via your web browser. Follow the instructions provided in the terminal or any additional guides included in the extracted files. 

Pay attention to the details about the vulnerability to fully understand how it can be exploited. This can provide valuable insight into security practices.

## 📚 Additional Resources
- **Docker Documentation**: For comprehensive guides and troubleshooting, view the [official Docker documentation](https://docs.docker.com/).
- **CVE-2025-32463 Explanation**: For a detailed dive into the vulnerability and how it is exploited, check the official CVE details [here](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-32463).

## 🗣️ FAQs
### I am new to Docker. Can I still use this?
Absolutely! This environment is designed for anyone, even if you have no prior experience with Docker.

### What if I encounter an error?
If you face issues, check Docker's troubleshooting section and ensure your Docker installation is functioning correctly.

### Can I use this for educational purposes?
Yes! This lab is ideal for understanding security vulnerabilities and improving your knowledge in cybersecurity.

文件快照

 [4.0K]  /data/pocs/e2149dc63a5482b49fdc3a6ee745475e96c0e01d
├── [4.0K]  docker
│   ├── [1.6K]  build.sh
│   ├── [4.0K]  deb
│   │   └── [2.1K]  Dockerfile
│   ├── [4.0K]  source
│   │   └── [1.6K]  Dockerfile
│   └── [1.1K]  sudo-chwoot.sh
├── [4.0K]  image
│   ├── [399K]  banner.png
│   ├── [366K]  image_2JLJBZujvB.png
│   ├── [437K]  image_431f2OMa-_.png
│   ├── [297K]  image_4wbcm-W8kC.png
│   ├── [859K]  image_6q3NTpOGrL.png
│   ├── [1.3M]  image_70MpL9pgzs.png
│   ├── [284K]  image_7sDv4vIv4J.png
│   ├── [398K]  image_85AvWOVKeq.png
│   ├── [1.7M]  image__bHzakfFZl.png
│   ├── [2.2M]  image_BmgXxPTqzC.png
│   ├── [467K]  image_bZL07ontRY.png
│   ├── [512K]  image_cpESTgiONG.png
│   ├── [417K]  image_DG6iu7M3JO.png
│   ├── [127K]  image_dxmCBrfNGX.png
│   ├── [474K]  image_EAbock-kFB.png
│   ├── [258K]  image_EUlKBOv6qe.png
│   ├── [338K]  image_FgzZgRFeRe.png
│   ├── [297K]  image_fRnHe3ukwq.png
│   ├── [ 52K]  image_GJouvfQyMF.png
│   ├── [836K]  image_HiGVkBsATm.png
│   ├── [390K]  image_iGbGssSCye.png
│   ├── [787K]  image_IXsDe1VMyI.png
│   ├── [781K]  image_kj7c-Nr14J.png
│   ├── [129K]  image_LDVxLo4-Rm.png
│   ├── [288K]  image_m2E-ZF3QDc.png
│   ├── [887K]  image_m8qagxmflc.png
│   ├── [357K]  image_MdDVfo6fFs.png
│   ├── [318K]  image_mEtw_DnHOG.png
│   ├── [173K]  image_oerGcu_F5X.png
│   ├── [537K]  image_pcalFIH05q.png
│   ├── [ 99K]  image_PJ-R6fO4VM.png
│   ├── [413K]  image_pyUtqydEgT.png
│   ├── [767K]  image_QA7YDCrzgQ.png
│   ├── [626K]  image_r4gp6QUwbp.png
│   ├── [ 60K]  image_R7fVyAYU_m.png
│   ├── [754K]  image_t27w6RRkBr.png
│   ├── [458K]  image_uHiP9fGfj_.png
│   ├── [441K]  image_wdqq-vpLhE.png
│   ├── [3.3M]  image_xZJ3pkERK7.png
│   ├── [462K]  image_Y6ta-LnzQ4.png
│   ├── [479K]  image_y8eG_7iyvY.png
│   ├── [328K]  image_yfvH8U0Gux.png
│   ├── [163K]  image_yTKKNRaN0K.png
│   ├── [510K]  image_yVJ1S-PQA1.png
│   └── [520K]  image_zjRVFNRVfB.png
├── [1.0K]  LICENSE
├── [3.7K]  README.md
└── [ 42K]  从 CVE-2025-32463 谈及 chroot 的容器隔离安全性.md

4 directories, 52 files

备注