https://github.com/curl/curl: Improper Limitation of a Pathname to a Restricted Directory
CVE-2023-27534 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in https://github.com/curl/curl, 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 https://github.com/curl/curl versions: Fixed in 8.0.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.44% chance of exploitation within 30 days, higher than 85% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update SIMATIC S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
- Update SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP to V3.1.5 or a later version.
- Update SIPLUS S7-1500 CPU 1518-4 PN/DP MFP to V3.1.5 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Https://github.com/curl/curl | https://github.com/curl/curl | Fixed in 8.0.0 | Not stated |
| Siemens | SIMATIC S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Siemens | SIPLUS S7-1500 CPU 1518-4 PN/DP MFP | V3.1.0 up to, but not including, V3.1.5 | V3.1.5 |
| Haxx | Curl | 7.18.0 through 7.88.1 | Not stated |
| Fedora Project | Fedora | 36 | Not stated |
| NetApp | Active Iq Unified Manager | Not specified in the record | Not stated |
| Broadcom | Brocade Fabric Operating System Firmware | Not specified in the record | Not stated |
| NetApp | H300s Firmware | Not specified in the record | Not stated |
| NetApp | H500s Firmware | Not specified in the record | Not stated |
| NetApp | H700s Firmware | Not specified in the record | Not stated |
| NetApp | H410s Firmware | Not specified in the record | Not stated |
| Splunk | Universal Forwarder | 8.2.0 up to, but not including, 8.2.12; 9.0.0 up to, but not including, 9.0.6; 9.1.0 | 8.2.12, 9.0.6 |
Version data comes from the organisation that assigned the CVE. 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.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.1 | 8.8 | High | CISA (ADP) |
Official description
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /~2/foo while accessing a server with a specific user.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
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
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2024/03/msg00016.htmlMailing List, Third Party Advisory
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFC…Mailing List, Third Party Advisory
- security.gentoo.org/glsa/202310-12Third Party Advisory
- security.netapp.com/advisory/ntap-20230420-0012/Third Party Advisory
Technical write-ups (may include proof of concept)
- hackerone.com/reports/1892351Exploit, Third Party Advisory
Other references
Other vulnerabilities in https://github.com/curl/curl
- 7.5 High severity
- 8.8 High severity
- 9.1 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.