Rconfig: Server-Side Request Forgery
CVE-2023-39109 is a high-severity server-side request forgery vulnerability in Rconfig, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Rconfig versions: 3.9.4. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 3.94% chance of exploitation within 30 days, which is in the top 9.44% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Rconfig you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
rconfig v3.9.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the path_a parameter in the doDiff Function of /classes/compareClass.php. This vulnerability allows authenticated attackers to make arbitrary requests via injection of crafted URLs.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Server-Side Request Forgery
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.
How developers prevent this class of flaw
- If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
- If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Technical write-ups (may include proof of concept)
- github.com/zer0yu/CVE_Request/blob/master/rConfig/rConfig_path_a.mdExploit, Third Party Advisory
Other vulnerabilities in Rconfig
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
rConfig OS Command Injection Exploited
Recent Server-Side Request Forgery vulnerabilities
- 7.5 High severity
- 7.2 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.