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

Goal: 1000 CNY ยท Raised: 1359 CNY

100%

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

CVSS 9.9 ยท Critical

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: YesWiki < 4.4.5 has a critical encryption flaw. ๐Ÿ“‰ **Consequences**: Attackers can recover password reset keys. This leads to unauthorized account takeover and full system compromise. ๐Ÿ’ฅ

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **Root Cause**: CWE-327 (Use of a Broken/Risky Cryptographic Algorithm). ๐Ÿ› **Flaw**: Weak encryption + Hardcoded hashing for password reset keys. ๐Ÿ”‘ The keys are predictable and reversible.

Q3Who is affected? (Versions/Components)

๐Ÿข **Vendor**: YesWiki (French Wiki System). ๐Ÿ’ป **Product**: YesWiki. ๐Ÿ“… **Affected**: Versions **before 4.4.5**. โš ๏ธ If you are running 4.4.4 or older, you are vulnerable.

Q4What can hackers do? (Privileges/Data)

๐Ÿ•ต๏ธ **Hacker Action**: Recover the hardcoded reset key. ๐Ÿ”„ Use it to reset ANY user's password. ๐Ÿ”“ **Privileges**: Full account access. ๐Ÿ“Š **Data**: Complete confidentiality breach (C:H) and integrity loss (I:L).

Q5Is exploitation threshold high? (Auth/Config)

๐Ÿ“‰ **Threshold**: LOW. ๐ŸŒ **Auth**: None required (PR:N). ๐Ÿ–ฑ๏ธ **UI**: None required. ๐Ÿš€ **Complexity**: Low (AC:L). It is an easy, remote exploit for anyone.

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

๐Ÿšซ **Public Exploit**: No specific PoC code provided in data. ๐Ÿ“œ **References**: GitHub commits and GHSA advisory exist.โ€ฆ

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Check**: Verify your YesWiki version. ๐Ÿ“‹ **Scan**: Look for version < 4.4.5. ๐Ÿงช **Test**: Check if password reset functionality uses the weak/hardcoded hash mechanism described in the advisory.โ€ฆ

Q8Is it fixed officially? (Patch/Mitigation)

โœ… **Fixed**: Yes. ๐Ÿ“ฆ **Patch**: Upgrade to **YesWiki 4.4.5** or later. ๐Ÿ”— **Source**: See GitHub commits and GHSA-4fvx-h823-38v3 for official fix details. ๐Ÿ”„ Immediate update recommended.

Q9What if no patch? (Workaround)

๐Ÿšง **Workaround**: If you cannot upgrade immediately: 1. Disable public password reset if possible. 2. Monitor admin logs for suspicious reset attempts. 3. Isolate the instance from the internet.โ€ฆ

Q10Is it urgent? (Priority Suggestion)

๐Ÿ”ฅ **Urgency**: HIGH. ๐Ÿšจ **Priority**: Critical. โšก CVSS Score indicates High Confidentiality impact. ๐Ÿƒโ€โ™‚๏ธ **Action**: Patch immediately. This allows easy account takeover without authentication.