This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login.
Read the full analysis โ
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.โฆ
๐ **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.โฆ
๐ ๏ธ **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.โฆ
๐ง **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.โฆ