Read the docs
TI-2020-19417 Aliases GHSA-gm9x-q798-hmr4

Command Injection in git-tags-remote

Priority LOW 38CWE-78Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Code execution
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-78.

Summary

All versions of `git-tags-remote ` are vulnerable to Command Injection. The package fails to sanitize the repository input and passes it directly to an `exec` call on the `get` function . This may allow attackers to execute arbitrary code in the system if the `repo` value passed to the function is user-controlled. The following proof-of-concept creates a file in `/tmp`: ``` const gitTagsRemote = require('git-tags-remote'); gitTagsRemote.get('https://github.com/sh0ji/git-tags-remote.git; echo "Injection Success" > /tmp/command-injection.test') .then(tags => console.log(tags)); ```

Why it matters now

Fix Fixed git-tags-remote (npm): 1.0.4

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—git-tags-remote (npm)before 1.0.41.0.4Patch availableGHSA-gm9x-q798-hmr4
  • git-tags-remote (npm) Vendor— Affected before 1.0.4 Fixed in 1.0.4 Patch available GHSA-gm9x-q798-hmr4

Remediation

  • Fix · GHSA-gm9x-q798-hmr4 git-tags-remote (npm) Fixed in 1.0.4 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-gm9x-q798-hmr4

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences