Discourse up to 3.1.0.beta2 IPv4 Address server-side request forgery
|CVSS Meta Temp Score|
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
|Current Exploit Price (≈)|
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
|CTI Interest Score|
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
A vulnerability, which was classified as problematic, has been found in Discourse up to 3.1.0.beta2. This issue affects some unknown processing of the component IPv4 Address Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality. The summary by CVE is:
Discourse is an open-source discussion platform. Prior to version 3.1.0.beta3 of the `beta` and `tests-passed` branches, attackers are able to bypass Discourse's server-side request forgery (SSRF) protection for private IPv4 addresses by using a IPv4-mapped IPv6 address. The issue is patched in the latest beta and tests-passed version of Discourse. version 3.1.0.beta3 of the `beta` and `tests-passed` branches. There are no known workarounds.
The weakness was published 03/18/2023 as GHSA-26h3-8ww8-v5fc. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2023-28111 since 03/10/2023. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 3.1.0.beta3 eliminates this vulnerability. Applying the patch fd16eade7fcc6bba4b71e71106a2eb13cdfdae4a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
CVSSv3VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
CNA Base Score: 5.7
CNA Vector (GitHub, Inc.): 🔒
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
ExploitingClass: Server-side request forgery
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
Threat IntelligenceInterest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
0-Day Time: 🔒
Upgrade: Discourse 3.1.0.beta3
Timeline03/10/2023 CVE reserved
03/18/2023 +8 days Advisory disclosed
03/18/2023 +0 days VulDB entry created
04/11/2023 +24 days VulDB last update
CVE: CVE-2023-28111 (🔒)
EntryCreated: 03/18/2023 08:39 AM
Updated: 04/11/2023 03:06 PM
Changes: 03/18/2023 08:39 AM (52), 04/11/2023 03:06 PM (11)
Do you need the next level of professionalism?
Upgrade your account now!
No comments yet. Languages: en.
Please log in to comment.