CVE-2025-32359

In Zammad 6.4.x before 6.4.2, there is client-side enforcement of server-side security. When changing their two factor authentication configuration, users need to re-authenticate with their current password first. However, this change was enforced in Zammad only on the front end level, and not when using the API directly.
References
Link Resource
https://zammad.com/en/advisories/zaa-2025-02 Vendor Advisory
Configurations

Configuration 1 (hide)

cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*

History

15 Apr 2025, 15:31

Type Values Removed Values Added
CWE NVD-CWE-Other
First Time Zammad
Zammad zammad
CPE cpe:2.3:a:zammad:zammad:*:*:*:*:*:*:*:*
References () https://zammad.com/en/advisories/zaa-2025-02 - () https://zammad.com/en/advisories/zaa-2025-02 - Vendor Advisory

07 Apr 2025, 14:17

Type Values Removed Values Added
Summary
  • (es) En Zammad 6.4.x anterior a la 6.4.2, la seguridad del servidor se aplica en el lado del cliente. Al cambiar la configuración de autenticación de dos factores, los usuarios deben volver a autenticarse con su contraseña actual. Sin embargo, este cambio se aplicó en Zammad solo en el front-end, y no al usar la API directamente.

05 Apr 2025, 21:15

Type Values Removed Values Added
New CVE

Information

Published : 2025-04-05 21:15

Updated : 2025-04-15 15:31


NVD link : CVE-2025-32359

Mitre link : CVE-2025-32359

CVE.ORG link : CVE-2025-32359


JSON object : View

Products Affected

zammad

  • zammad
CWE
CWE-602

Client-Side Enforcement of Server-Side Security

NVD-CWE-Other