Security
Headlines
HeadlinesLatestCVEs

Tag

#vulnerability

GHSA-6c5r-4wfc-3mcx: Hashicorp Vault has Incorrect Validation for Non-CA Certificates

Vault and Vault Enterprise (“Vault”) TLS certificate auth method did not correctly validate client certificates when configured with a non-CA certificate as [+trusted certificate+|https://developer.hashicorp.com/vault/api-docs/auth/cert#certificate]. In this configuration, an attacker may be able to craft a malicious certificate that could be used to impersonate another user. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

ghsa
#vulnerability#auth#ssl
GHSA-mwgr-84fv-3jh9: Hashicorp Vault has an Observable Discrepancy on Existing and Non-Existing Users

A timing side channel in Vault and Vault Enterprise’s (“Vault”) userpass auth method allowed an attacker to distinguish between existing and non-existing users, and potentially enumerate valid usernames for Vault’s Userpass auth method. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

GHSA-mr4h-qf9j-f665: Hashicorp Vault has Code Execution Vulnerability via Plugin Configuration

A privileged Vault operator within the root namespace with write permission to {{sys/audit}} may obtain code execution on the underlying host if a plugin directory is set in Vault’s configuration. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

GHSA-6h4p-m86h-hhgh: Hashicorp Vault has Privilege Escalation Vulnerability

A privileged Vault operator with write permissions to the root namespace’s identity endpoint could escalate their own or another user’s token privileges to Vault’s root policy. Fixed in Vault Community Edition 1.20.0 and Vault Enterprise 1.20.0, 1.19.6, 1.18.11 and 1.16.22.

GHSA-qgj7-fmq2-6cc4: Hashicorp Vault has Lockout Feature Authentication Bypass

Vault and Vault Enterprise’s (“Vault”) user lockout feature could be bypassed for Userpass and LDAP authentication methods. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

GHSA-v6r4-35f9-9rpw: Hashicorp Vault has Login MFA Rate Limit Bypass Vulnerability

Vault and Vault Enterprise’s (“Vault”) login MFA rate limits could be bypassed and TOTP tokens could be reused. Fixed in Vault Community Edition 1.20.1 and Vault Enterprise 1.20.1, 1.19.7, 1.18.12, and 1.16.23.

GHSA-2x2j-3c2v-g3c2: Microweber XSS Vulnerability in the homepage Endpoint

Microweber CMS 2.0 is vulnerable to Cross Site Scripting (XSS) in the /projects/profile, homepage endpoint via the last name field.

GHSA-mvj3-hc7j-vp74: Microweber has Reflected XSS Vulnerability in the layout Parameter

Reflected Cross-Site Scripting (XSS) in Microweber CMS 2.0 via the layout parameter on the /admin/page/create page allows arbitrary JavaScript execution in the context of authenticated admin users.

GHSA-8357-fjvx-xrm8: Microweber has Reflected XSS Vulnerability in the id Parameter

Reflected Cross-Site Scripting (XSS) in the id parameter of the live_edit.module_settings API endpoint in Microweber CMS2.0 allows execution of arbitrary JavaScript.

GHSA-8j63-96wh-wh3j: 1Panel agent certificate verification bypass leading to arbitrary command execution

### Project Address: Project Address [1Panel](https://github.com/1Panel-dev/1Panel) ### Official website: https://www.1panel.cn/ ### Time: 2025 07 26 ### Version: 1panel V2.0.5 ### Vulnerability Summary - First, we introduce the concepts of 1panel v2 Core and Agent. After the new version is released, 1panel adds the node management function, which allows you to control other hosts by adding nodes. - The HTTPS protocol used for communication between the Core and Agent sides did not fully verify the authenticity of the certificate during certificate verification, resulting in unauthorized interfaces. The presence of a large number of command execution or high-privilege interfaces in the 1panel led to RCE. ![](https://github.com/user-attachments/assets/ebd0b388-d6c0-4678-98ee-47646e69ebe9) ### Code audit process 1. First we go to the Agent HTTP routing fileagent/init/router/router.go ![](https://github.com/user-attachments/assets/dd9152a9-6677-4674-b75f-3b67dcedb321) 2. It was foun...