Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-13357: CWE-1188: Initialization of a Resource with an Insecure Default in HashiCorp Tooling

0
High
VulnerabilityCVE-2025-13357cvecve-2025-13357cwe-1188
Published: Fri Nov 21 2025 (11/21/2025, 15:02:27 UTC)
Source: CVE Database V5
Vendor/Project: HashiCorp
Product: Tooling

Description

Vault’s Terraform Provider incorrectly set the default deny_null_bind parameter for the LDAP auth method to false by default, potentially resulting in an insecure configuration. If the underlying LDAP server allowed anonymous or unauthenticated binds, this could result in authentication bypass. This vulnerability, CVE-2025-13357, is fixed in Vault Terraform Provider v5.5.0.

AI-Powered Analysis

AILast updated: 11/21/2025, 15:21:17 UTC

Technical Analysis

CVE-2025-13357 is a vulnerability classified under CWE-1188, which involves the initialization of a resource with an insecure default configuration. Specifically, in HashiCorp Vault’s Terraform Provider version 4.2.0, the LDAP authentication method incorrectly sets the deny_null_bind parameter to false by default. This parameter controls whether LDAP anonymous or unauthenticated binds are denied. When set to false, and if the underlying LDAP server permits anonymous binds, an attacker can bypass authentication mechanisms, gaining unauthorized access to Vault-managed secrets and resources. The vulnerability affects confidentiality and integrity by allowing unauthorized access without requiring user interaction or prior authentication. The CVSS 3.1 score of 7.4 reflects a high severity, with network attack vector, high attack complexity, and no privileges or user interaction required. The vulnerability was publicly disclosed on November 21, 2025, and fixed in Vault Terraform Provider version 5.5.0. No known exploits have been reported in the wild to date. The issue highlights the risk of insecure default configurations in security-critical infrastructure-as-code tools, emphasizing the need for secure defaults and thorough configuration reviews.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of sensitive data managed via HashiCorp Vault, especially in environments leveraging LDAP for authentication. Unauthorized access could lead to exposure of secrets, credentials, and other sensitive configuration data, potentially enabling further lateral movement or privilege escalation within corporate networks. Organizations with automated infrastructure provisioning and secrets management pipelines are particularly vulnerable. The impact is heightened in sectors with stringent data protection requirements, such as finance, healthcare, and government, where unauthorized data access can lead to regulatory penalties and reputational damage. Additionally, the vulnerability could undermine trust in DevOps and cloud security practices, delaying adoption of automation tools. Although no availability impact is expected, the breach of confidentiality and integrity alone justifies urgent remediation.

Mitigation Recommendations

European organizations should immediately upgrade to Vault Terraform Provider version 5.5.0 or later, where the deny_null_bind parameter default is corrected. Until upgrade, administrators must manually set deny_null_bind to true in LDAP auth method configurations to prevent anonymous binds. Conduct thorough audits of LDAP server settings to ensure anonymous or unauthenticated binds are disabled at the directory service level. Implement network segmentation and access controls to limit exposure of Vault and LDAP servers to trusted hosts only. Monitor authentication logs for unusual bind attempts or access patterns indicative of exploitation attempts. Incorporate configuration management and security scanning tools to detect insecure defaults in infrastructure-as-code deployments. Provide training to DevOps and security teams on secure configuration best practices for HashiCorp tools. Finally, maintain an incident response plan tailored to secrets management breaches to quickly contain and remediate any compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
HashiCorp
Date Reserved
2025-11-18T15:38:23.306Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6920823c0f995c4f64ea2855

Added to database: 11/21/2025, 3:16:12 PM

Last enriched: 11/21/2025, 3:21:17 PM

Last updated: 11/21/2025, 5:57:16 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats