GHSA-GV2H-GF8M-R68J

Vulnerability from github – Published: 2022-02-15 00:19 – Updated: 2022-02-15 00:19
VLAI
Summary
Exposure of server configuration in github.com/go-vela/server
Details

Impact

What kind of vulnerability is it? Who is impacted?

Sample of template exposing server configuration using Sprig's env function:

metadata:
  template: true

steps:
  - name: sample
    image: alpine:latest
    commands:
      # OAuth client ID for Vela <-> GitHub communication
      - echo {{ env "VELA_SOURCE_CLIENT" }}
      # secret used for server <-> worker communication
      - echo {{ env "VELA_SECRET" }}

Patches

Has the problem been patched? What versions should users upgrade to?

  • Upgrade to 0.6.1

Additional Recommended Action(s)

  • Rotate all secrets

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

  • No

For more information

If you have any questions or comments about this advisory:

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/go-vela/compiler"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.6.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2020-26294"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200",
      "CWE-78"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-05-21T17:58:10Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\n* The ability to expose configuration set in the [Vela server](https://github.com/go-vela/server) via [pipeline template functionality](https://go-vela.github.io/docs/templates/overview/).\n* It impacts all users of Vela.\n\n\nSample of template exposing server configuration [using Sprig\u0027s `env` function](http://masterminds.github.io/sprig/os.html):\n\n```yaml\nmetadata:\n  template: true\n\nsteps:\n  - name: sample\n    image: alpine:latest\n    commands:\n      # OAuth client ID for Vela \u003c-\u003e GitHub communication\n      - echo {{ env \"VELA_SOURCE_CLIENT\" }}\n      # secret used for server \u003c-\u003e worker communication\n      - echo {{ env \"VELA_SECRET\" }}\n```\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\n* Upgrade to `0.6.1`\n\n#### Additional Recommended Action(s)\n\n* Rotate all secrets\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\n* No\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Email us at [vela@target.com](mailto:vela@target.com)",
  "id": "GHSA-gv2h-gf8m-r68j",
  "modified": "2022-02-15T00:19:57Z",
  "published": "2022-02-15T00:19:57Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/go-vela/compiler/security/advisories/GHSA-gv2h-gf8m-r68j"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2020-26294"
    },
    {
      "type": "WEB",
      "url": "https://github.com/go-vela/compiler/commit/f1ace5f8a05c95c4d02264556e38a959ee2d9bda"
    },
    {
      "type": "WEB",
      "url": "https://github.com/helm/helm/blob/6297c021cbda1483d8c08a8ec6f4a99e38be7302/pkg/engine/funcs.go#L46-L47"
    },
    {
      "type": "WEB",
      "url": "https://pkg.go.dev/github.com/go-vela/compiler/compiler"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Exposure of server configuration in github.com/go-vela/server"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…