What is the severity of CVE-2022-32227?

CVE-2022-32227 is considered a medium severity vulnerability due to the potential exposure of sensitive oauth tokens.

How do I fix CVE-2022-32227?

To mitigate CVE-2022-32227, update Rocket.Chat to version 4.8.2 or later, or version 4.7.6 or later.

What versions are affected by CVE-2022-32227?

Versions of Rocket.Chat prior to 4.8.2 and 4.7.5 are affected by CVE-2022-32227.

What kind of information is at risk with CVE-2022-32227?

CVE-2022-32227 poses a risk of leaking sensitive information, specifically oauth tokens.

What permission setting is involved in CVE-2022-32227?

The vulnerability CVE-2022-32227 is related to the permission "view-full-other-user-info" which can lead to the oauth token leak.

Vulnerability/
CVE-2022-32227

medium

6.5

CWE

319

23/9/2022

3/8/2024

CVE-2022-32227

First published: Fri Sep 23 2022(Updated: )

A cleartext transmission of sensitive information exists in Rocket.Chat <v5, <v4.8.2 and <v4.7.5 relating to Oauth tokens by having the permission "view-full-other-user-info", this could cause an oauth token leak in the product.

Credit: support@hackerone.com support@hackerone.com

Affected Software	Affected Version	How to fix
Rocket.Chat Rocket.Chat	<4.7.5
Rocket.Chat Rocket.Chat	>=4.8.0<4.8.2

Never miss a vulnerability like this again

Reference Links

https://hackerone.com/reports/1517377

Frequently Asked Questions

What is the severity of CVE-2022-32227?
CVE-2022-32227 is considered a medium severity vulnerability due to the potential exposure of sensitive oauth tokens.
How do I fix CVE-2022-32227?
To mitigate CVE-2022-32227, update Rocket.Chat to version 4.8.2 or later, or version 4.7.6 or later.
What versions are affected by CVE-2022-32227?
Versions of Rocket.Chat prior to 4.8.2 and 4.7.5 are affected by CVE-2022-32227.
What kind of information is at risk with CVE-2022-32227?
CVE-2022-32227 poses a risk of leaking sensitive information, specifically oauth tokens.
What permission setting is involved in CVE-2022-32227?
The vulnerability CVE-2022-32227 is related to the permission "view-full-other-user-info" which can lead to the oauth token leak.

agent/author
agent/type
collector/nvd-api
agent/software-canonical-lookup-request
collector/nvd-index
agent/weakness
agent/references
agent/severity
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/tags
agent/first-publish-date
agent/event
agent/source
vendor/rocket.chat
canonical/rocket.chat rocket.chat
version/rocket.chat rocket.chat/4.8.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-32227?
CVE-2022-32227 is considered a medium severity vulnerability due to the potential exposure of sensitive oauth tokens.
How do I fix CVE-2022-32227?
To mitigate CVE-2022-32227, update Rocket.Chat to version 4.8.2 or later, or version 4.7.6 or later.
What versions are affected by CVE-2022-32227?
Versions of Rocket.Chat prior to 4.8.2 and 4.7.5 are affected by CVE-2022-32227.
What kind of information is at risk with CVE-2022-32227?
CVE-2022-32227 poses a risk of leaking sensitive information, specifically oauth tokens.
What permission setting is involved in CVE-2022-32227?
The vulnerability CVE-2022-32227 is related to the permission "view-full-other-user-info" which can lead to the oauth token leak.