| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Microsoft Office 365 and classified as critical. Affected by this issue is some unknown functionality. Executing a manipulation can lead to session expiration. This vulnerability appears as CVE-2022-2076. The attack may be performed from remote. In addition, an exploit is available. There are still doubts about whether this vulnerability truly exists. Configuration settings should be changed. Vendor claims that pre-requisites are very high, the feature works as intended, and that configuration settings might mitigate the issue.
Details
A vulnerability has been found in Microsoft Office 365 (Office Suite Software) (the affected version is unknown) and classified as critical. This vulnerability affects an unknown code. The manipulation with an unknown input leads to a session expiration vulnerability. The CWE definition for the vulnerability is CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." As an impact it is known to affect confidentiality, integrity, and availability.
The bug was discovered 10/21/2021. The weakness was presented 02/01/2022 by Lukas Reiter and Alexander Hagenah as VULN-056667 / Missing Session Hijacking Protection in Microsoft O365 as confirmed advisory (GitHub). The advisory is shared for download at github.com. This vulnerability was named CVE-2022-2076. Technical details are unknown but a public exploit is available.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 103 days. During that time the estimated underground price was around $5k-$25k. The real existence of this vulnerability is still doubted at the moment. Vendor claims that pre-requisites are very high, the feature works as intended, and that configuration settings might mitigate the issue.
It is possible to mitigate the problem by applying the configuration setting .
Additional details are provided at mandiant.com. Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
Screenshot

CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.8
VulDB Base Score: 6.3
VulDB Temp Score: 5.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Session expirationCWE: CWE-613
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: ConfigStatus: 🔍
0-Day Time: 🔍
Workaround: docs.microsoft.com
Timeline
10/21/2021 🔍10/26/2021 🔍
02/01/2022 🔍
02/01/2022 🔍
06/15/2022 🔍
Sources
Vendor: microsoft.comAdvisory: VULN-056667 / Missing Session Hijacking Protection in Microsoft O365
Researcher: Lukas Reiter, Alexander Hagenah
Status: Confirmed
Disputed: 🔍
CVE: CVE-2022-2076 (🔍)
GCVE (CVE): GCVE-0-2022-2076
GCVE (VulDB): GCVE-100-192028
scip Labs: https://www.scip.ch/en/?labs.20161013
Misc.: 🔍
Entry
Created: 02/01/2022 07:42Updated: 06/15/2022 15:04
Changes: 02/01/2022 07:42 (40), 02/01/2022 07:44 (5), 06/14/2022 07:16 (11), 06/15/2022 15:04 (2)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.