What is the severity of CVE-2022-3819?

CVE-2022-3819 is considered a moderate severity vulnerability due to the improper authorization issue it presents.

How do I fix CVE-2022-3819?

To fix CVE-2022-3819, you should upgrade GitLab CE/EE to versions 15.3.5, 15.4.4, or 15.5.2 and above.

What versions are affected by CVE-2022-3819?

CVE-2022-3819 affects GitLab CE/EE versions from 15.0 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.

What type of vulnerability is CVE-2022-3819?

CVE-2022-3819 is classified as an improper authorization vulnerability.

Who can exploit CVE-2022-3819?

Malicious users with access to the GitLab instance can exploit CVE-2022-3819 to set emojis on internal notes they do not have permissions for.

Vulnerability/
CVE-2022-3819

medium

4.3

CWE

863

9/11/2022

3/8/2024

CVE-2022-3819

First published: Wed Nov 09 2022(Updated: )

An improper authorization issue in GitLab CE/EE affecting all versions from 15.0 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows a malicious users to set emojis on internal notes they don't have access to.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=15.0.0<15.3.5
GitLab	>=15.0.0<15.3.5
GitLab	>=15.4.0<15.4.4
GitLab	>=15.4.0<15.4.4
GitLab	>=15.5.0<15.5.2
GitLab	>=15.5.0<15.5.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-3819?
CVE-2022-3819 is considered a moderate severity vulnerability due to the improper authorization issue it presents.
How do I fix CVE-2022-3819?
To fix CVE-2022-3819, you should upgrade GitLab CE/EE to versions 15.3.5, 15.4.4, or 15.5.2 and above.
What versions are affected by CVE-2022-3819?
CVE-2022-3819 affects GitLab CE/EE versions from 15.0 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.
What type of vulnerability is CVE-2022-3819?
CVE-2022-3819 is classified as an improper authorization vulnerability.
Who can exploit CVE-2022-3819?
Malicious users with access to the GitLab instance can exploit CVE-2022-3819 to set emojis on internal notes they do not have permissions for.

agent/type
agent/references
agent/author
agent/weakness
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/15.0.0
version/gitlab/15.4.0
version/gitlab/15.5.0

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-3819?
CVE-2022-3819 is considered a moderate severity vulnerability due to the improper authorization issue it presents.
How do I fix CVE-2022-3819?
To fix CVE-2022-3819, you should upgrade GitLab CE/EE to versions 15.3.5, 15.4.4, or 15.5.2 and above.
What versions are affected by CVE-2022-3819?
CVE-2022-3819 affects GitLab CE/EE versions from 15.0 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2.
What type of vulnerability is CVE-2022-3819?
CVE-2022-3819 is classified as an improper authorization vulnerability.
Who can exploit CVE-2022-3819?
Malicious users with access to the GitLab instance can exploit CVE-2022-3819 to set emojis on internal notes they do not have permissions for.