Perfsonar: Server-Side Request Forgery
CVE-2022-41412 is a high-severity server-side request forgery vulnerability in Perfsonar, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.4.5 as the first without the flaw, so updating Perfsonar to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 4.71% chance of exploitation within 30 days, which is in the top 8.04% of all scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Perfsonar to 4.4.5 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
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
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.6 | High | NVD |
| CVSS 3.1 | 8.6 | High | CISA (ADP) |
Official description
An issue in the graphData.cgi component of perfSONAR v4.4.5 and prior allows attackers to access sensitive data and execute Server-Side Request Forgery (SSRF) attacks.
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: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- packetstormsecurity.com/files/170069/perfSONAR-4.4.4-Open-Proxy-Relay.htmlThird Party Advisory
- github.com/renmizo/CVE-2022-41412Third Party Advisory
Recent Server-Side Request Forgery vulnerabilities
- 9.1 Critical severity
- 7.5 High severity
- 7.5 High severity
- 8.7 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.