Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-33666 | First vendor Publication | 2024-04-26 |
| Vendor | Cve | Last vendor Modification | 2025-04-15 |
Security-Database Scoring CVSS v3
| Cvss vector : N/A | |||
|---|---|---|---|
| Overall CVSS Score | NA | ||
| Base Score | NA | Environmental Score | NA |
| impact SubScore | NA | Temporal Score | NA |
| Exploitabality Sub Score | NA | ||
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| An issue was discovered in Zammad before 6.3.0. Users with customer access to a ticket could have accessed time accounting details of this ticket via the API. This data should be available only to agents. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-33666 |
CPE : Common Platform Enumeration
Sources (Detail)
| Source | Url |
|---|
Alert History
| Date | Informations |
|---|---|
| 2025-05-27 02:38:19 |
|
| 2024-11-25 09:25:58 |
|
| 2024-07-03 09:27:39 |
|
| 2024-04-27 03:12:56 |
|
| 2024-04-27 03:12:53 |
|
| 2024-04-26 17:27:40 |
|
| 2024-04-26 09:27:26 |
|
