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

Goal: 1000 CNY ยท Raised: 1359 CNY

100%

CVE-2021-29156 โ€” AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: LDAP Injection in ForgeRock OpenAM. ๐Ÿ“‰ **Consequences**: Attackers can extract password hashes character-by-character, steal session tokens, or retrieve private keys.โ€ฆ

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **Root Cause**: LDAP Injection. ๐Ÿ› **Flaw**: Backend validates user existence via LDAP query during password reset. โš ๏ธ **CWE**: Not explicitly listed, but classic injection flaw in input handling.

Q3Who is affected? (Versions/Components)

๐Ÿข **Vendor**: ForgeRock. ๐Ÿ“ฆ **Product**: OpenAM (SSO Framework). ๐Ÿ“… **Affected**: Versions **before 13.5.1** (e.g., v13.0.0). ๐ŸŒ **Scope**: CoreServer identity service.

Q4What can hackers do? (Privileges/Data)

๐Ÿ•ต๏ธ **Actions**: Enumerate users & retrieve data. ๐Ÿ”‘ **Data Stolen**: Password hashes (char-by-char), Session Tokens, Private Keys. ๐Ÿšช **Privileges**: Can bypass authentication checks via token theft.

Q5Is exploitation threshold high? (Auth/Config)

โš–๏ธ **Threshold**: Medium. ๐Ÿ“ **Auth**: Likely requires initial access to the password reset flow. โš™๏ธ **Config**: Exploits the LDAP query logic during user validation. ๐Ÿ“ง **Vector**: Triggered via password reset request.

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

๐Ÿ”“ **Public Exp?**: YES. ๐Ÿ› ๏ธ **PoCs**: Multiple available (GuidePoint Security, 5amu, Nuclei templates). ๐ŸŒ **Wild Exp**: Active exploitation tools exist and are functional. โšก **Ease**: Automated scripts available.

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Check**: Scan for OpenAM v13.0.0-13.5.0. ๐Ÿงช **Test**: Use Nuclei templates or specific PoC tools. ๐Ÿ“ง **Indicator**: Observe LDAP query behavior during password reset attempts.โ€ฆ

Q8Is it fixed officially? (Patch/Mitigation)

โœ… **Fixed**: YES. ๐Ÿ“ฆ **Patch**: Upgrade to **OpenAM 13.5.1** or later. ๐Ÿ“œ **Ref**: Bugster OPENAM-10135. ๐Ÿ”„ **Action**: Immediate update recommended.

Q9What if no patch? (Workaround)

๐Ÿšง **Workaround**: If patching is delayed, restrict access to password reset endpoints. ๐Ÿ›‘ **Mitigation**: Implement strict input validation on LDAP queries. ๐Ÿ“‰ **Limit**: Reduce exposure of the CoreServer interface.โ€ฆ

Q10Is it urgent? (Priority Suggestion)

๐Ÿ”ฅ **Urgency**: HIGH. ๐Ÿšจ **Priority**: Critical. โณ **Reason**: Active PoCs exist, sensitive data (hashes/keys) is at risk. ๐Ÿƒ **Action**: Patch immediately or apply mitigations. ๐Ÿ“ข **Alert**: Notify security teams now.