ghsa-8pxw-9c75-6w56
Vulnerability from github
Published
2025-08-28 13:33
Modified
2025-09-17 19:12
Severity ?
Summary
NeuVector admin account has insecure default password
Details

Impact

A vulnerability exists in NeuVector versions up to and including 5.4.5, where a fixed string is used as the default password for the built-in admin account. If this password is not changed immediately after deployment, any workload with network access within the cluster could use the default credentials to obtain an authentication token. This token can then be used to perform any operation via NeuVector APIs.

In earlier versions, NeuVector supports setting the default (bootstrap) password for the admin account using a Kubernetes Secret named neuvector-bootstrap-secret. This Secret must contain a key named bootstrapPassword. However, if NeuVector fails to retrieve this value, it falls back to the fixed default password.

Patches

This issue is resolved in NeuVector version 5.4.6 and later. For rolling upgrades, it's strongly recommended to change the default admin password to a secure one.

Starting from version 5.4.6, NeuVector introduces additional Kubernetes RBAC permissions to ensure the bootstrap password can be securely managed via Secrets:

``` kubectl create role neuvector-binding-secret-controller \ --verb=create,patch,update --resource=secrets -n {neuvector}

kubectl create rolebinding neuvector-binding-secret-controller \ --role=neuvector-binding-secret-controller \ --serviceaccount=neuvector:controller \ --serviceaccount=neuvector:default -n {neuvector} ```

  • These RBAC roles are automatically applied when deploying via Helm.
  • If deploying or upgrading manually, you must create these roles before starting NeuVector.

NOTE: If these roles are not present, the NeuVector controller (from version 5.4.6 onward) does not start.

Behavior in Patched Versions

  • Upgrades: NeuVector does not reset any existing account passwords. It's strongly recommended to change the default admin password to a secure one.
  • New deployments:
  • If bootstrapPassword is not set in the `neuvector-bootstrap-secret, NeuVector generates a secure password and stores it in the same Secret.

On first login, the default admin must retrieve the password using:

kubectl get secret -n {neuvector} neuvector-bootstrap-secret \ -o go-template='{{ .data.bootstrapPassword | base64decode }}{{ "\n" }}'

The password must be changed during the first login via the NeuVector UI.

NOTE: If the default admin password is set using a Kubernetes ConfigMap or a persistent backup (not a fixed string), this value takes precedence over the Secret-based mechanism.

Workarounds

For existing vulnerable versions, log in to the NeuVector UI immediately after deployment and update the default admin password.

References

If you have any questions or comments about this advisory:

Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/neuvector/neuvector"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "5.0.0"
            },
            {
              "fixed": "5.4.6"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-8077"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-1393"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-08-28T13:33:36Z",
    "nvd_published_at": "2025-09-17T13:15:34Z",
    "severity": "CRITICAL"
  },
  "details": "### Impact\n\nA vulnerability exists in NeuVector versions up to and including **5.4.5**, where a fixed string is used as the default password for the built-in `admin` account. If this password is not changed immediately after deployment, any workload with network access within the cluster could use the default credentials to obtain an authentication token. This token can then be used to perform any operation via NeuVector APIs.\n\nIn earlier versions, NeuVector supports setting the default (bootstrap) password for the `admin` account using a Kubernetes Secret named `neuvector-bootstrap-secret`. This Secret must contain a key named `bootstrapPassword`. However, if NeuVector fails to retrieve this value, it falls back to the fixed default password.\n\n### Patches\n\nThis issue is resolved in NeuVector version **5.4.6** and later. For rolling upgrades, it\u0027s strongly recommended to change the default `admin` password to a secure one.\n\nStarting from version **5.4.6**, NeuVector introduces additional Kubernetes RBAC permissions to ensure the bootstrap password can be securely managed via Secrets:\n\n```\nkubectl create role neuvector-binding-secret-controller \\\n  --verb=create,patch,update --resource=secrets -n {neuvector}\n\nkubectl create rolebinding neuvector-binding-secret-controller \\\n  --role=neuvector-binding-secret-controller \\\n  --serviceaccount=neuvector:controller \\\n  --serviceaccount=neuvector:default -n {neuvector}\n```\n\n- These RBAC roles are automatically applied when deploying via Helm.\n- If deploying or upgrading manually, you must create these roles before starting NeuVector.\n\n**NOTE:** If these roles are not present, the NeuVector controller (from version 5.4.6 onward) does not start.\n\n#### Behavior in Patched Versions\n\n- **Upgrades:** NeuVector does not reset any existing account passwords. It\u0027s strongly recommended to change the default `admin` password to a secure one.\n- **New deployments:**\n  - If `bootstrapPassword` is not set in the `neuvector-bootstrap-secret, NeuVector generates a secure password and stores it in the same Secret.\n\nOn first login, the default `admin` must retrieve the password using:\n\n```\nkubectl get secret -n {neuvector} neuvector-bootstrap-secret \\\n  -o go-template=\u0027{{ .data.bootstrapPassword | base64decode }}{{ \"\\n\" }}\u0027\n```\n\nThe password must be changed during the first login via the NeuVector UI.\n\n**NOTE:** If the default `admin` password is set using a Kubernetes ConfigMap or a persistent backup (not a fixed string), this value takes precedence over the Secret-based mechanism.\n\n### Workarounds\n\nFor existing vulnerable versions, log in to the NeuVector UI immediately after deployment and update the default `admin` password.\n\n### References\n\nIf you have any questions or comments about this advisory:\n\n- Reach out to the [SUSE Rancher Security team](https://github.com/rancher/rancher/security/policy) for security related inquiries.\n- Open an issue in the [NeuVector](https://github.com/neuvector/neuvector/issues/new/choose) repository.\n- Verify with our [support matrix](https://www.suse.com/suse-neuvector/support-matrix/all-supported-versions/neuvector-v-all-versions/) and [product support lifecycle](https://www.suse.com/lifecycle/#suse-security).",
  "id": "GHSA-8pxw-9c75-6w56",
  "modified": "2025-09-17T19:12:35Z",
  "published": "2025-08-28T13:33:36Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/neuvector/neuvector/security/advisories/GHSA-8pxw-9c75-6w56"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8077"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.suse.com/show_bug.cgi?id=CVE-2025-8077"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/neuvector/neuvector"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "NeuVector admin account has insecure default password"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…