Oauth2
Vendor:
First CVE: Jul 4, 2023 · Active for 3 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
8.8
Avg CVSS
Higher Avg CVSS than 79% of tracked products
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Oauth2 over time
Volume of CVEsAvg CVSS Base Score
First CVE
Jul 4, 2023
3 years ago
Most Recent CVE
Jul 4, 2023
1,119 days ago
CVE Severity & Scoring
Oauth21 CVEs
100%
All CVEs352,785 CVEs
45%
40%
11%
High
Attack Vector
Local0 (0.0%)
Network1 (100.0%)
Unknown0 (0.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low1 (100.0%)
High0 (0.0%)
Unknown0 (0.0%)
User Interaction
None0 (0.0%)
Unknown0 (0.0%)
Required1 (100.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None1 (100.0%)
Unknown0 (0.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-31999HIGH All versions of @fastify/oauth2 used a statically generated state parameter at startup time and were used across all requests for all users. The purpose of the Oauth2 state paramet | Jul 4, 2023 | 8.8 | 24 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (1 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Oauth2
Top CWEs
Versions
No cataloged versions.