Content
Priority: ● Critical for CVE-2023-38545
● Low for CVE-2023-38546
Status: In Progress- Undergoing Analysis
First Published: 30 October 2023
Advisory Version: 1.1
References: CVE-2023- 38545 CVE-2023-38546
Summary
CVE-2023-38545:
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy handshake. When curl is asked to pass along the host name to the SOCKS5 proxy to allow that to resolve the address instead of it getting done by curl itself, the maximum length that host name can be is 255 bytes. If the host name is detected to be longer, curl switches to local name resolving and instead passes on the resolved address only. Due to this bug, the local variable that means "let the host resolve the name" could get the wrong value during a slow SOCKS5 handshake, and contrary to the intention, copy the too long host name to the target buffer instead of copying just the resolved address there. The target buffer being a heap based buffer, and the host name coming from the URL that curl has been told to operate with.
CVE-2023-38546:
This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met. libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers. libcurl provides a function call that duplicates en easy handle called [curl_easy_duphandle](https://curl.se/libcurl/c/curl_easy_duphandle.html). If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as `none` (using the four ASCII letters, no quotes). Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named `none` - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.
Affected Products
Vulnerable Products
The following matrix lists Hitachi Vantara products and solutions which have been confirmed to be affected by either of these vulnerabilities. If a Fixed Release Version is accompanied by a future date, the date is the best estimate we can provide based on current information and mitigation testing progress. If no Fixed Release Version is indicated for an affected product, Hitachi Vantara is continuing to evaluate the fix, and will update this advisory as additional information becomes available.
| Product | Fixed Release Version |
| Content Products |
| Content Platform | CVE-2023-38546: Affected. This low priority CVE will be addressed in a future release |
| Content Platform S Series | CVE-2023-38546: Affected. This low priority CVE will be addressed in a future release |
| Content Intelligence | CVE-2023-38546: Affected. This low priority CVE will be addressed in a future release |
| Hitachi Content Software for File | CVE-2023-38546: Affected. This low priority CVE will be addressed in a future release |
| Content Platform Anywhere Enterprise | CVE-2023-38546: Affected. This low priority CVE will be addressed in a future release |
| HCP for Cloud Scale | CVE-2023-38546: Affected. This low priority CVE will be addressed in a future release |
Products Confirmed Not Vulnerable
At the time of this advisory's publication, only products listed in the Vulnerable Products section above are confirmed to be affected by this vulnerability.
| Product | Fixed Release Version |
| Content Products |
| Content Platform | CVE-2023-38545: Not affected. The vulnerable version of curl is not used |
| Content Platform S Series | CVE-2023-38545: Not affected. The vulnerable version of curl is not used |
| Content Intelligence | CVE-2023-38545: Not affected. The vulnerable version of curl is not used
|
| Content Platform Anywhere | CVE-2023-38545: Not affected. The vulnerable version of curl is not used CVE-2023-38546: Not affected. The vulnerable version of curl is not used |
| Hitachi Content Software for File | CVE-2023-38545: Not affected. The vulnerable version of curl is not used |
| Content Platform Anywhere Enterprise | CVE-2023-38545: Not affected. The vulnerable version of curl is not used |
| Data Ingestor | CVE-2023-38545: Not affected. The vulnerable version of curl is not used CVE-2023-38546: Not affected. The vulnerable version of curl is not used |
Recommended Actions
Please continue to check this Security Advisory, as new information will be added to it as it becomes available.
If any of the information presented above remains unclear, please contact the Hitachi Vantara Global Support Center, or your Vantara-authorized service and support provider.
The information contained herein is for informational purposes only. It is not intended as a guaranty or warranty about Hitachi Vantara’s products, including any guaranty or warranty that any product cannot be exploited by third parties. All product warranties and obligations to a customer must be specified in a mutually acceptable and executed contract between the parties.