Security Bulletin
Summary
Vault’s Terraform Provider incorrectly set the default deny_null_bind parameter for the LDAP auth method to false by default. 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.
Vulnerability Details
CVEID: CVE-2025-13357
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.
CWE: CWE-1188: Insecure Default Initialization of Resource
CVSS Source: HashiCorp Inc.
CVSS Base score: 7.4
CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)
Affected Products and Versions
| Product(s) | Version(s) |
| IBM Vault Terraform Provider | 4.20 - 5.40 |
Remediation/Fixes
Customers should evaluate the risk associated with this issue and ensure deny_null_bind is set to true in their LDAP auth method configuration. Customers should also consider upgrading to Vault Community Edition 1.21.1 and Vault Enterprise 1.21.1, 1.20.6, 1.19.12, and 1.16.28, which no longer allows Vault to perform unauthenticated or null binds against the LDAP server.Otherwise, customers can upgrade the Vault Terraform Provider to v5.5.0, or explicitly set the deny_null_bind parameter to false in the Terraform files for any version of the Vault Terraform provider, and apply the changes.
Workarounds and Mitigations
None
Get Notified about Future Security Bulletins
References
Link to HashiCorp bulletin
Background
The Vault Terraform Provider uses Vault’s API and allows users to administer Vault using a configuration file. Vault’s LDAP auth method allows users to authenticate to Vault using an LDAP server. The LDAP auth method’s deny_null_bind parameter was used by Vault to explicitly allow unauthenticated binds, if permitted by the LDAP server.
Details
If a Vault LDAP auth backend was created with the Vault Terraform Provider with versions v4.2.0 to 5.4.0, the value of deny_null_bind parameter defaulted to false if the parameter was not specified in the Terraform file. Starting with Vault Terraform Provider v5.5.0, the provider will now correctly set this parameter to true by default. Vault 1.21.1, 1.20.5, 1.19.12, and 1.16.28 will also no longer accept empty password strings, preventing unauthenticated or anonymous binds to the LDAP server though the LDAP auth method. This parameter will be deprecated in a future version of Vault.
Acknowledgement
This issue was identified by a third party who reported it to HashiCorp. We deeply appreciate any effort to coordinate disclosure of security vulnerabilities. For information about security at HashiCorp and the reporting of security vulnerabilities, please see https://hashicorp.com/security.
Change History
21 Nov 2025: Initial Publication
*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.
Disclaimer
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES ""AS IS"" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. In addition to other efforts to address potential vulnerabilities, IBM periodically updates the record of components contained in our product offerings. As part of that effort, if IBM identifies previously unidentified packages in a product/service inventory, we address relevant vulnerabilities regardless of CVE date. Inclusion of an older CVEID does not demonstrate that the referenced product has been used by IBM since that date, nor that IBM was aware of a vulnerability as of that date. We are making clients aware of relevant vulnerabilities as we become aware of them. "Affected Products and Versions" referenced in IBM Security Bulletins are intended to be only products and versions that are supported by IBM and have not passed their end-of-support or warranty date. Thus, failure to reference unsupported or extended-support products and versions in this Security Bulletin does not constitute a determination by IBM that they are unaffected by the vulnerability. Reference to one or more unsupported versions in this Security Bulletin shall not create an obligation for IBM to provide fixes for any unsupported or extended-support products or versions.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
21 November 2025
Initial Publish date:
21 November 2025
UID
ibm17251827