S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
high·Product Based Web Vulnerabilities·Updated Mar 9, 2024

CVE-2023-39108 Scanner

CVE-2023-39108 scanner - Server-Side Request Forgery vulnerability in rConfig

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, ipv4, subdomain
CostFree
2.6k
Times Used
continuous scan runs
4.3k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2023-39108
8.8
CVSS

rconfig v3.9.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the path_b parameter in the doDiff Function of /classes/compareClass.php. This vulnerability allows authenticated attackers to make arbitrary requests via injection of crafted URLs.

Attack Vector
-
Privileges Req.
-
User Interaction
-
Affected
n/aby n/a
n/a
Updated Aug 22, 2026View on NVD →
Detail

rConfig is a popular network device configuration management tool, designed to assist network administrators in efficiently managing configurations of network devices such as routers, switches, and firewalls. It offers features for automatically backing up configurations, tracking changes, and managing device states across various hardware. rConfig is widely used in IT infrastructures for its ability to streamline the configuration process, reduce human errors, and enhance the security posture by ensuring configurations adhere to compliance standards.

The vulnerability identified as CVE-2023-39108 is a high-severity Server-Side Request Forgery (SSRF) present in rConfig version 3.9.4. It resides in the /classes/compareClass.php file, specifically within the doDiff Function, where the path_b parameter fails to properly sanitize user-supplied input. This flaw allows authenticated attackers to craft malicious URLs that the server will request, potentially accessing sensitive files or internal systems that are otherwise inaccessible from the external network. This vulnerability exposes the system to information disclosure, data manipulation, or even remote code execution by interacting with internal services.

The technical flaw stems from the application's improper validation of URLs provided by users, allowing attackers to specify external or internal URLs for the server to request. This can lead to unauthorized access to local files (Local File Inclusion - LFI) or internal network resources, enabling attackers to bypass security measures, access sensitive information, or interact with internal services in a manner unintended by the application developers. The vulnerability is particularly dangerous because it can be exploited by an authenticated user, making it critical to address in environments where rConfig is used.

Exploiting this SSRF vulnerability could lead to several adverse outcomes, including but not limited to data breaches, unauthorized access to sensitive internal resources, manipulation of internal processes, and potential remote code execution. The ability to make arbitrary requests to internal services can be leveraged to perform actions on behalf of the server, escalating the attacker's capabilities within the network. This poses a significant risk to the confidentiality, integrity, and availability of the network infrastructure managed by rConfig.

S4E (S4E) offers a comprehensive Cyber Threat Exposure Management service that can help identify and remediate vulnerabilities such as CVE-2023-39108 in rConfig. By becoming a member, users gain access to state-of-the-art scanning technology and expert advice, enabling them to proactively secure their network configurations against emerging threats. S4E provides detailed insights into vulnerabilities, offering guidance on best practices and remediation strategies to enhance the overall security posture of your network infrastructure.

 

References

Solution Advice
  1. Upgrade to the latest version of rConfig that addresses this SSRF vulnerability.
  2. Employ strict input validation and sanitization to ensure only valid URLs are processed.
  3. Limit the ability of the server to make outbound requests to untrusted sources or internal resources.
  4. Implement network segmentation and firewall rules to restrict access to sensitive internal services.
  5. Regularly audit and monitor the application and underlying systems for signs of unauthorized access or exploitation.
  6. Educate users and administrators on the importance of strong authentication measures and the potential risks associated with SSRF vulnerabilities.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.