Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator
Hard-coded JWT secret allows authentication bypass in Veeam Recovery Orchestrator
The product contains hard-coded credentials, such as a password or cryptographic key.
https://cwe.mitre.org/data/definitions/798.html →Open in CWE collection →An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.
https://capec.mitre.org/data/definitions/70.html →Open in CAPEC collection →https://capec.mitre.org/data/definitions/191.html →Open in CAPEC collection →
| Product | Vendor | Status |
|---|---|---|
| Tracked | ||
| recovery_orchestrator | * | Tracked |