Git Tag Annotation Action
Approved changes feed: RSS · Atom
cpe:2.3:a:git-tag-annotation-action_project:git-tag-annotation-action:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Git Tag Annotation Action Project (879faabb-dd31-5e43-a72b-843b393923f3) |
|---|---|
| Product | Git Tag Annotation Action (6a062eb9-c9a7-581f-a1e9-b37d7bdb8f0e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/ericcornelissen/git-tag-annotation-action |
purl2cpe | 2026-06-01 10:14:41.592474 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-15272 |
vulnerable | 2026-06-08 05:19:25.631162 |
Shell-injection in git-tag-annotation GitHub action
HIGH (8.7)
In the git-tag-annotation-action (open source GitHub Action) before version 1.0.1, an attacker can execute arbitrary (*) shell commands if they can control the value of [the `tag` input] or manage to alter the value of [the `GITHUB_REF` environment variable]. The problem has been patched in version 1.0.1. If you don't use the `tag` input you are most likely safe. The `GITHUB_REF` environment variable is protected by the GitHub Actions environment so attacks from there should be impossible. If you must use the `tag` input and cannot upgrade to `> 1.0.0` make sure that the value is not controlled by another Action.
Published: 2020-10-26T18:20:20.000Z
Updated: 2024-08-04T13:15:19.802Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.