Envoy up to 1.22.8/1.23.5/1.24.3/1.25.2 OAuth Filter denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Envoy up to 1.22.8/1.23.5/1.24.3/1.25.2. Affected by this vulnerability is an unknown functionality of the component OAuth Filter. Performing a manipulation results in denial of service. This vulnerability is identified as CVE-2023-27496. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability was found in Envoy up to 1.22.8/1.23.5/1.24.3/1.25.2. It has been classified as problematic. This affects some unknown functionality of the component OAuth Filter. The manipulation with an unknown input leads to a denial of service vulnerability. CWE is classifying the issue as CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. This is going to have an impact on availability. The summary by CVE is:
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, the OAuth filter assumes that a `state` query param is present on any response that looks like an OAuth redirect response. Sending it a request with the URI path equivalent to the redirect path, without the `state` parameter, will lead to abnormal termination of Envoy process. Versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9 contain a patch. The issue can also be mitigated by locking down OAuth traffic, disabling the filter, or by filtering traffic before it reaches the OAuth filter (e.g. via a lua script).
The weakness was released 04/05/2023 as GHSA-j79q-2g66-2xv5. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-27496 since 03/01/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 1.22.9, 1.23.6, 1.24.4, 1.25.3 or 1.26.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 1.22.0
- 1.22.1
- 1.22.2
- 1.22.3
- 1.22.4
- 1.22.5
- 1.22.6
- 1.22.7
- 1.22.8
- 1.23.0
- 1.23.1
- 1.23.2
- 1.23.3
- 1.23.4
- 1.23.5
- 1.24.0
- 1.24.1
- 1.24.2
- 1.24.3
- 1.25.0
- 1.25.1
- 1.25.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitHub, Inc.): 🔍
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: Denial of serviceCWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Envoy 1.22.9/1.23.6/1.24.4/1.25.3/1.26.0
Timeline
03/01/2023 🔍04/05/2023 🔍
04/05/2023 🔍
04/05/2023 🔍
Sources
Advisory: GHSA-j79q-2g66-2xv5Status: Confirmed
CVE: CVE-2023-27496 (🔍)
GCVE (CVE): GCVE-0-2023-27496
GCVE (VulDB): GCVE-100-224961
Entry
Created: 04/05/2023 07:28Changes: 04/05/2023 07:28 (50)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.