Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: GLPI v10.0.2 & earlier suffers from **PHP Code Injection** via the `htmLawedTest.php` file.
💥 **Consequences**: Attackers can execute arbitrary PHP commands, leading to full system compromise.

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: Flaw in the **htmlawed** module (`/vendor/htmlawed/htmlawed/htmLawedTest.php`).
⚠️ **CWE**: Not specified in data, but clearly a **Code Injection** flaw allowing untrusted input execution.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: **GLPI** (IT Asset Management Software).
📅 **Versions**: **10.0.2 and prior**.
🔧 **Component**: `htmlawed` library integration.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

👑 **Privileges**: **Unauthenticated Remote Code Execution (RCE)**.
📂 **Data**: Full access to server commands (e.g., `cat /etc/passwd`).
🔓 **Impact**: Complete takeover of the affected instance without login.

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

📉 **Threshold**: **LOW**.
🔑 **Auth**: **None required** (Unauthenticated).
⚙️ **Config**: Direct HTTP POST to specific test endpoint. Easy to trigger.

Question 6

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

Accepted Answer

🔥 **Public Exp**: **YES**.
📜 **PoCs**: Multiple GitHub repos (e.g., `0xGabe`, `Lzer0Kx01`) provide curl commands and scripts.
🌐 **Wild Exp**: Active scanning tools exist for batch detection.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**: Send POST request to `/vendor/htmlawed/htmlawed/htmLawedTest.php` with `hhook=exec`.
📡 **Scan**: Use provided GitHub PoC scripts or PacketStorm reports to identify vulnerable instances.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

🩹 **Fixed**: **YES**.
📢 **Patch**: GLPI **10.0.3** released to address this.
🔗 **Ref**: Official GLPI announcement confirms the fix.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch?**: **Block Access**: Restrict access to `/vendor/htmlawed/` directory via WAF or Nginx/Apache config.
🚫 **Disable**: If possible, remove or disable the `htmLawedTest.php` file entirely.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

⚡ **Urgency**: **CRITICAL**.
🚨 **Priority**: **Immediate Action**. Unauthenticated RCE is high-risk. Update to v10.0.3+ or apply network restrictions NOW.

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

CVE-2022-35914 — 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