LowGHSA-mmmm-chjf-jmvwCVE-2020-13353
Gitaly Insufficient Session Expiration vulnerability
Published 24 May 2022 · Updated 8 Nov 2023
Is your project on an affected gitaly?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
gitalyRubyGems
- Affected
- >=1.79.0 <13.3.9
- Fixed in
- 13.3.9
Update to the fixed version for your release line, for example:
bundle update --conservative gitaly # Gemfile: '>= 13.3.9'gitalyRubyGems
- Affected
- >=13.4 <13.4.5
- Fixed in
- 13.4.5
Update to the fixed version for your release line, for example:
bundle update --conservative gitaly # Gemfile: '>= 13.4.5'gitalyRubyGems
- Affected
- >=13.5 <13.5.2
- Fixed in
- 13.5.2
Update to the fixed version for your release line, for example:
bundle update --conservative gitaly # Gemfile: '>= 13.5.2'Details
When importing repos via URL, one time use git credentials were persisted beyond the expected time window in Gitaly 1.79.0 or above. Affected versions are: >=1.79.0, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.
Is GHSA-mmmm-chjf-jmvw in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected gitaly, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.