cyrus-imapd: Cyrus IMAP: Information disclosure via URLAUTH token forgery
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| cyrusimap | Cyrus IMAP | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Cyrusimap | Cyrus Imap |
|
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-4766-1 | cyrus-imapd security update |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.297% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | cyrus-imapd: Cyrus IMAP: Information disclosure via URLAUTH token forgery | |
| Weaknesses | CWE-341 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | An issue was discovered in cyrus-imapd in Cyrus IMAP through 3.12.2. URLAUTH token forgery can occur via a missing mboxkey. If an attacker knew a folder name on the victim's account for which the victim had never issued an auth URL, they could forge a working URLAUTH token by computing an HMAC-SHA1 value with a predictable key, giving them read access to the mailbox. (URLAUTH is an obscure feature, meaning that the odds of any user actually being susceptible to this attack are very low. Perhaps no public clients use URLAUTH.) | |
| First Time appeared |
Cyrusimap
Cyrusimap cyrus Imap |
|
| Weaknesses | CWE-340 | |
| CPEs | cpe:2.3:a:cyrusimap:cyrus_imap:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Cyrusimap
Cyrusimap cyrus Imap |
|
| References |
| |
| Metrics |
cvssV3_1
|