Q: Who is affected? (Versions/Components)

🏥 **Affected**: **Orthanc Server** (Open Source DICOM Server). 📅 **Versions**: All versions **prior to 1.5.8**. 🏢 **Vendor**: Orthanc Company.

Q: Is exploitation threshold high? (Auth/Config)

📉 **Threshold**: **EXTREMELY LOW**. 🌐 **Auth**: None required. ⚙️ **Config**: Default settings are vulnerable. If you expose the port to the internet, you are hacked. 👀 **UI**: No user interaction needed.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed?**: **YES**. 🔧 **Patch**: Upgrade to **Orthanc 1.5.8** or later. 📝 **Reference**: CISA ICSMA-25-037-02 advisory available.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL (P0)**. ⏱️ **Priority**: Fix **IMMEDIATELY**. 📉 **Risk**: CVSS 9.8 (Critical). Medical data is high-value. Default misconfiguration makes mass exploitation easy. Do not wait.

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Orthanc < 1.5.8 has an **Access Control Error**. Remote access is enabled by default, but **Basic Auth is OFF**.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-306** (Missing Authentication for Critical Function).
❌ **Flaw**: The software defaults to allowing remote connections **without** requiring a username/password.…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

🏥 **Affected**: **Orthanc Server** (Open Source DICOM Server).
📅 **Versions**: All versions **prior to 1.5.8**.
🏢 **Vendor**: Orthanc Company.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💀 **Hackers Can**:
1. **Read** sensitive medical images (Patient Privacy Leak).
2. **Modify/Delete** patient records (Data Integrity Loss).
3. **Disable** the server (Service Denial).…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

📉 **Threshold**: **EXTREMELY LOW**.
🌐 **Auth**: None required.
⚙️ **Config**: Default settings are vulnerable. If you expose the port to the internet, you are hacked.
👀 **UI**: No user interaction needed.

Question 6

Is there a public Exp? (PoC/Wild Exploitation)

Accepted Answer

🕵️ **Public Exp?**: **No specific PoC** listed in the data.
🔥 **Wild Exploitation**: High risk. Since no auth is needed, *anyone* can manually connect via HTTP client.…

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1. Scan for **Orthanc** service ports (usually 8042).
2. Try accessing the root URL (`/`).
3. If it returns data **without** a 401 Unauthorized error, you are **VULNERABLE**.
4.…

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed?**: **YES**.
🔧 **Patch**: Upgrade to **Orthanc 1.5.8** or later.
📝 **Reference**: CISA ICSMA-25-037-02 advisory available.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch? Workaround**:
1. **Enable Basic Auth** in configuration immediately.
2. **Block Remote Access**: Restrict network access to localhost/internal LAN only.
3.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **CRITICAL (P0)**.
⏱️ **Priority**: Fix **IMMEDIATELY**.
📉 **Risk**: CVSS 9.8 (Critical). Medical data is high-value. Default misconfiguration makes mass exploitation easy. Do not wait.

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

CVE-2025-0896 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

Q6Is there a public Exp? (PoC/Wild Exploitation)

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring