Weak JWT Signing Secret Generation Enables Token Forgery in Zimbra Collaboration
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Zimbra | Collaboration | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Zimbra | Collaboration |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.333% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Synacor
Synacor zimbra Collaboration Suite |
|
| CPEs | cpe:2.3:a:synacor:zimbra_collaboration_suite:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Synacor
Synacor zimbra Collaboration Suite |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Weak JWT Signing Secret Generation Enables Token Forgery in Zimbra Collaboration |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In Zimbra Collaboration (ZCS) before 10.1.17, weak cryptographic key generation vulnerability exists in the OnlyOffice integration. The zimbraDocumentEditingJwtSecret is generated using an insecure random number generator, resulting in insufficient entropy. An attacker who obtains a JWT signed with the generated secret may be able to recover the JWT signing secret through offline brute-force, potentially enabling JWT forgery. | |
| First Time appeared |
Zimbra
Zimbra collaboration |
|
| Weaknesses | CWE-1241 | |
| CPEs | cpe:2.3:a:zimbra:collaboration:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Zimbra
Zimbra collaboration |
|
| References |
| |
| Metrics |
cvssV3_1
|