Skip to content

Exposure of server configuration in github.com/go-vela/server

High severity GitHub Reviewed Published Dec 30, 2020 in go-vela/compiler • Updated Jan 9, 2023

Package

gomod github.com/go-vela/compiler (Go)

Affected versions

< 0.6.1

Patched versions

0.6.1

Description

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:

References

@wass3r wass3r published to go-vela/compiler Dec 30, 2020
Reviewed May 21, 2021
Published to the GitHub Advisory Database Feb 15, 2022
Last updated Jan 9, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.166%
(54th percentile)

CVE ID

CVE-2020-26294

GHSA ID

GHSA-gv2h-gf8m-r68j

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.