Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2024-27302 β€” AI Deep Analysis Summary

CVSS 9.1 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: go-zero < 1.4.4 allows malicious domains to bypass filters via configurable parameters. πŸ“‰ **Consequences**: High impact on Confidentiality & Integrity.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: CWE-639 (Authorization Bypass Through User-Controlled SQL/Other Input).…

Q3Who is affected? (Versions/Components)

🏒 **Affected**: zeromicro / go-zero. πŸ“¦ **Version**: All versions **before 1.4.4**. If you are running an older Web/RPC framework version, you are at risk.

Q4What can hackers do? (Privileges/Data)

πŸ’€ **Attacker Capabilities**: Bypass domain filters. πŸ“Š **Impact**: CVSS Score indicates **High** Confidentiality and Integrity loss.…

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Threshold**: **LOW**. CVSS Vector: AV:N (Network), AC:L (Low Complexity), PR:N (No Privileges Required). No authentication or complex configuration is needed to exploit this remotely.

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

πŸ§ͺ **Public Exploit**: **No** public PoC or wild exploitation detected in the provided data. However, the logic flaw is clear, making custom exploits highly probable for skilled attackers.

Q7How to self-check? (Features/Scanning)

πŸ” **Self-Check**: Check your `go.mod` or dependency tree. If `go-zero` version is `< 1.4.4`, you are vulnerable. Look for configurations where domain filters are user-controllable.

Q8Is it fixed officially? (Patch/Mitigation)

βœ… **Fixed**: **YES**. Patched in version **1.4.4**. πŸ“ **Reference**: See GitHub commit `d9d79e9` and GHSA advisory `fgxv-gw55-r5fq` for official details.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: If you cannot upgrade immediately, **disable** the configurable filter parameter if possible.…

Q10Is it urgent? (Priority Suggestion)

⚑ **Urgency**: **HIGH**. CVSS 3.1 indicates severe impact. Since it requires no auth and is network-accessible, patch to v1.4.4 **immediately** to prevent potential bypass attacks.