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

Goal: 1000 CNY ยท Raised: 1359 CNY

100%

CVE-2024-28255 โ€” AI Deep Analysis Summary

CVSS 9.8 ยท Critical

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: OpenMetadata's JWT Filter has a logic flaw. It skips validation for excluded endpoints. ๐Ÿ›‘ **Consequences**: Attackers can bypass authentication entirely.โ€ฆ

Q2Root Cause? (CWE/Flaw)

๐Ÿ” **Root Cause**: **CWE-287** (Improper Authentication). The `JwtFilter` checks if the path *contains* an excluded string.โ€ฆ

Q3Who is affected? (Versions/Components)

๐Ÿ‘ฅ **Affected**: **OpenMetadata** platform. ๐Ÿ“ฆ **Version**: Vulnerable versions prior to **1.2.4**. ๐Ÿข **Vendor**: open-metadata. Any instance running older versions is at risk. โš ๏ธ

Q4What can hackers do? (Privileges/Data)

๐Ÿ’€ **Hackers' Power**: Bypass auth โžก๏ธ Access sensitive endpoints. ๐ŸŽฏ **Specifics**: Trigger **SpEL expression injection**. ๐Ÿ“‰ **Impact**: Full **RCE** (Remote Code Execution). Complete control over the server.โ€ฆ

Q5Is exploitation threshold high? (Auth/Config)

๐Ÿ“Š **Threshold**: **LOW**. ๐ŸŒ **Network**: Attackable remotely (AV:N). ๐Ÿ”‘ **Auth**: **None required** (PR:N) due to bypass. ๐Ÿ–ฑ๏ธ **UI**: No user interaction needed (UI:N). ๐Ÿ“ˆ **Complexity**: Low (AC:L). Easy to exploit! ๐Ÿš€

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

๐Ÿ’ฃ **Public Exp**: **YES**. ๐Ÿ“‚ **PoC**: Available on GitHub (YongYe-Security). ๐Ÿงช **Scanner**: Nuclei templates exist. ๐ŸŒ **Wild Exp**: Batch scanning tools are active. โš ๏ธ **Warning**: Tool is for security testing only! ๐Ÿ›‘

Q7How to self-check? (Features/Scanning)

๐Ÿ”Ž **Self-Check**: Use **Nuclei** with CVE-2024-28255 template. ๐Ÿ **Python**: Run the specific PoC script. ๐Ÿ“ก **Scan**: Look for the path parameter bypass pattern.โ€ฆ

Q8Is it fixed officially? (Patch/Mitigation)

๐Ÿ› ๏ธ **Fixed**: **YES**. ๐Ÿ“ฆ **Patch**: Upgrade to **OpenMetadata v1.2.4** or later. ๐Ÿ”’ **Resolution**: The filter logic was corrected to validate JWT properly. ๐Ÿ“… **Published**: March 15, 2024.โ€ฆ

Q9What if no patch? (Workaround)

๐Ÿšง **No Patch?**: **No known workarounds**. ๐Ÿšซ **Limitation**: Cannot simply block IPs or use WAF rules easily due to path manipulation. ๐Ÿ›‘ **Advice**: If you can't patch, isolate the service.โ€ฆ

Q10Is it urgent? (Priority Suggestion)

๐Ÿ”ฅ **Urgency**: **CRITICAL**. ๐Ÿšจ **Priority**: **P0 / Immediate Action**. ๐Ÿ“‰ **CVSS**: 9.8 (Critical). ๐Ÿ’ฅ **Impact**: Full RCE. ๐Ÿƒโ€โ™‚๏ธ **Action**: Patch NOW. Do not wait. This is a high-severity, easily exploitable flaw. โณ