Terraform EnterpriseApplication · Hashicorp

CVE-2020-15511

MEDIUM · 5.3 CVSS v3.1 Published 2020-07-30
Fix available
A fix is available. Upgrade to 202007-1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HashiCorp Terraform Enterprise up to v202006-1 contained a default signup page that allowed user registration even when disabled, bypassing SAML enforcement. Fixed in v202007-1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

HashiCorp Terraform Enterprise versions up to v202006-1 contained a default user registration/signup page that remained accessible even when user registration was explicitly disabled in the system settings, allowing unauthorized account creation and bypassing SAML single sign-on enforcement controls.

MitigationUpgrade Terraform Enterprise to v202007-1 or later, and verify that user registration is properly disabled when SAML authentication is enforced.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Terraform EnterpriseApplication
Affected:< 202007-1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Terraform Enterprise version
    Check the installed Terraform Enterprise version through the admin console or system information panel. This is typically visible in the UI under 'Settings' or 'System' information, or via the /api/v1/version endpoint if accessible.
    Affected if The installed version is any release prior to v202007-1 (for example, v202006-1, v202005-1, or earlier)
  2. Verify user registration setting state
    Navigate to the Terraform Enterprise admin settings and locate the user registration or signup configuration. Check whether the option to disable user registration is enabled.
    Affected if User registration is set to 'disabled' but the registration page remains accessible
  3. Confirm SAML authentication is enforced
    In the Terraform Enterprise admin panel, verify that SAML single sign-on is configured and that the enforcement option to restrict authentication to SAML users only is enabled.
    Affected if SAML is configured and enforced in system settings
  4. Test registration page accessibility
    Attempt to access the user registration or signup endpoint directly (typically /signup or /register) while logged out. Observe whether the registration form is displayed despite registration being disabled in settings.
    Affected if The registration page loads and displays a signup form even when user registration is explicitly disabled in the admin settings
  5. Verify unauthorized account creation
    Submit a test registration through the accessible signup page using a non-SSO email address. Confirm whether an account can be created without SAML authentication.
    Affected if An account can be created without authenticating through SAML, bypassing the SSO enforcement control

You are affected if running any Terraform Enterprise version prior to v202007-1 and the user registration page is accessible despite being disabled in system settings, allowing unauthorized account creation outside SAML authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 202007-1 or later
Fixed in 202007-1
Interim mitigation

Upgrade Terraform Enterprise to v202007-1 or later, and verify that user registration is properly disabled when SAML authentication is enforced.

Fix this in Terraform Enterprise Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-15511 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-15511 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data