What is the severity of CVE-2022-3291?

CVE-2022-3291 is considered a high severity vulnerability due to potential sensitive data exposure.

How do I fix CVE-2022-3291?

To fix CVE-2022-3291, upgrade GitLab EE to version 15.2.5 or later, 15.3.4 or later, or 15.4.1 or later.

What versions of GitLab are affected by CVE-2022-3291?

CVE-2022-3291 affects all GitLab EE versions from 14.9 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.

What type of data is exposed due to CVE-2022-3291?

CVE-2022-3291 can leak sensitive information via cache serialization.

Is there a workaround for CVE-2022-3291?

Currently, the recommended approach is to upgrade to a fixed version, as no workaround has been documented for CVE-2022-3291.

Vulnerability/
CVE-2022-3291

medium

6.5

CWE

502

17/10/2022

3/8/2024

CVE-2022-3291

First published: Mon Oct 17 2022(Updated: )

Serialization of sensitive data in GitLab EE affecting all versions from 14.9 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 can leak sensitive information via cache

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=14.9<15.2.5
GitLab	>=15.3<15.3.4
GitLab	>=15.4<15.4.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3291?
CVE-2022-3291 is considered a high severity vulnerability due to potential sensitive data exposure.
How do I fix CVE-2022-3291?
To fix CVE-2022-3291, upgrade GitLab EE to version 15.2.5 or later, 15.3.4 or later, or 15.4.1 or later.
What versions of GitLab are affected by CVE-2022-3291?
CVE-2022-3291 affects all GitLab EE versions from 14.9 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
What type of data is exposed due to CVE-2022-3291?
CVE-2022-3291 can leak sensitive information via cache serialization.
Is there a workaround for CVE-2022-3291?
Currently, the recommended approach is to upgrade to a fixed version, as no workaround has been documented for CVE-2022-3291.

agent/references
agent/type
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/14.9
version/gitlab/15.3
version/gitlab/15.4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-3291?
CVE-2022-3291 is considered a high severity vulnerability due to potential sensitive data exposure.
How do I fix CVE-2022-3291?
To fix CVE-2022-3291, upgrade GitLab EE to version 15.2.5 or later, 15.3.4 or later, or 15.4.1 or later.
What versions of GitLab are affected by CVE-2022-3291?
CVE-2022-3291 affects all GitLab EE versions from 14.9 prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1.
What type of data is exposed due to CVE-2022-3291?
CVE-2022-3291 can leak sensitive information via cache serialization.
Is there a workaround for CVE-2022-3291?
Currently, the recommended approach is to upgrade to a fixed version, as no workaround has been documented for CVE-2022-3291.