CVE-2021-22208
First published: Thu May 06 2021(Updated: )
An issue has been discovered in GitLab affecting versions starting with 13.5 up to 13.9.7. Improper permission check could allow the change of timestamp for issue creation or update.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=13.5.0<13.9.7 | |
| GitLab | >=13.5.0<13.9.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2021-22208?
CVE-2021-22208 has been classified as a medium severity vulnerability due to its potential to affect the integrity of issue timestamps.
How do I fix CVE-2021-22208?
To fix CVE-2021-22208, upgrade GitLab to version 13.9.8 or later.
What versions of GitLab are affected by CVE-2021-22208?
CVE-2021-22208 affects GitLab versions from 13.5.0 up to 13.9.7.
What impact does CVE-2021-22208 have on GitLab users?
CVE-2021-22208 could allow unauthorized users to modify timestamps for issue creation or updates.
Is there a workaround for CVE-2021-22208 if I cannot upgrade GitLab?
There is no official workaround for CVE-2021-22208; upgrading to a patched version is strongly recommended.
- agent/references
- agent/type
- agent/author
- agent/softwarecombine
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/gitlab
- canonical/gitlab
- version/gitlab/13.5.0