Aphuongkma

**Name of the Vulnerable Software and Affected Versions** Wazuh versions 4.0.0 through 4.14.6 Wazuh version 5.0.0-beta2 **Description** Authenticated attackers with `allow run as` enabled can cause a denial of service by exhausting CPU resources. This occurs when arbitrarily deeply nested JSON structures are submitted to the 'POST /security/user/authenticate/run as' endpoint. By repeatedly sending malformed `auth context` bodies with unlimited nesting depth, the API framework consumes excessive CPU, denying service to other API consumers. **Recommendations** Update Wazuh versions 4.0.0 through 4.14.6 to version 4.14.7. Update Wazuh version 5.0.0-beta2 to a newer version. As a temporary mitigation, disable the `allow run as` feature.

**Name of the Vulnerable Software and Affected Versions** Gitea (affected versions not specified) **Description** The `ToHook()` function in `services/webhook/general.go` decrypts the `HeaderAuthorizationEncrypted` field and returns the plaintext authorization header in the API response. This allows repository administrators to read sensitive credentials, such as Bearer tokens, Basic auth credentials, and API keys, set by other administrators. The issue occurs because the function decrypts the secret stored in the database using the server's `SecretKey` before serializing it into the response, effectively converting a write-only secret into a readable credential. **API Endpoints:** - '/api/v1/repos/{owner}/{repo}/hooks' - '/api/v1/repos/{owner}/{repo}/hooks/{id}' - '/api/v1/admin/hooks' - '/api/v1/orgs/{org}/hooks' - '/api/v1/user/hooks' **Vulnerable Parameters or Variables:** - `HeaderAuthorizationEncrypted` **Function Names:** - `ToHook()` - `HeaderAuthorization()` **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability. As a temporary workaround, restrict access to the affected API endpoints to minimize the risk of credential exposure.