admin3 through 3.0.0 Session Token Disclosure via Audit Log
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 8.7epss 0.4%
exploitation probability
0.4%top 71% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
admin3 through 3.0.0 persists user session tokens in the audit log event body when publishing UserLoggedIn domain events. Attackers with log:view permission can read the JSON response from the GET /logs endpoint to harvest session tokens and replay them as bearer credentials for full user access.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Affected products
cjbi · admin3public PoCs found — 1
cve_referencegithub.com/LinYuanyi1/cve-request-poc/blob/master/admin3/C02_log_session_token_disclosure.pyunverified⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
References
https://github.com/cjbi/admin3https://github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/java/tech/wetech/admin3/infra/service/DefaultSessionService.javahttps://github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/java/tech/wetech/admin3/sys/service/LogService.javahttps://github.com/cjbi/admin3/blob/3.0.0/admin3-server/src/main/resources/data.sqlhttps://github.com/LinYuanyi1/cve-request-poc/blob/master/admin3/C02_log_session_token_disclosure.pyhttps://www.vulncheck.com/advisories/admin3-through-3.0.0-session-token-disclosure-via-audit-log