Client for URLs (cURL)

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Client for URLs (cURL) is an open source command line application for transferring data with uniform resource locator (URL) syntax that supports a variety of network protocols including File Transfer Protocol (FTP), Gopher, Hypertext Transfer Protocol (HTTP), Hypertext Transfer Protocol Secure (HTTPS), Lightweight Directory Access Protocol (LDAP), Lightweight Directory Access Protocol over SSL (LDAPS), Post Office Protocol 3 (POP3), Post Office Protocol 3 Secure (POP3S), Secure Copy Protocol (SCP), Secure File Transfer Protocol (SFTP), Simple Mail Transfer Protocol (SMTP) and others. This TRM entry addresses cURL as a standalone product only. If cURL is bundled with a particular platform or application, it is the responsibility of the vendor to provide patching. The administrator of the machine is responsible for ensuring all relevant patches are applied. See the components section of other TRM entries, such as Red Hat Enterprise Linux, to confirm the bundled installation of cURL is TRM approved with that product.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.11
Decision Date:	11/17/2023 at 03:58:00 UTC
Introduced By:	TRM Request
Vendor Name:	MIT (Mass. Inst. Tech.)

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
7.1x.x	10/01/2002
7.2x.x	02/09/2010
7.3x.x	04/12/2013
7.4x.x	01/08/2015
7.5x.x	10/23/2017
7.60.x	07/05/2018
7.61.x	07/21/2018
7.64.x	03/27/2019
7.70.x	04/29/2020
7.74.x	12/09/2020
7.79.x	09/15/2021
7.84.x	06/27/2022
7.86.x	10/26/2022
7.88.x	02/20/2023
8.4.x	10/11/2023

Current Decision Matrix (11/09/2023)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2022

CY2023

CY2024

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

7.1x.x

Unapproved

7.2x.x

Unapproved

7.3x.x

Unapproved

7.4x.x

Unapproved

7.5x.x

Unapproved

7.60.x

Unapproved

7.61.x

Unapproved

7.64.x

Unapproved

7.70.x

Divest
[5, 10, 11, 12, 13]

Unapproved

7.74.x

Divest
[5, 10, 11, 12, 13]

Divest
[5, 10, 11, 13, 14]

Divest
[5, 10, 11, 13, 15]

Divest
[13, 15, 16, 17]

Unapproved

7.79.x

Approved w/Constraints
[5, 10, 11, 12, 13]

Divest
[5, 10, 11, 13, 14]

Divest
[5, 10, 11, 13, 15]

Divest
[13, 15, 16, 17]

Divest
[13, 17, 18, 19, 20, 21]

Unapproved

7.84.x

Unapproved

Approved w/Constraints
[5, 10, 11, 13, 14]

Approved w/Constraints
[5, 10, 11, 13, 15]

Divest
[13, 15, 16, 17]

Divest
[13, 17, 18, 19, 20, 21]

Unapproved

7.86.x

Unapproved

Divest
[13, 15, 16, 17]

Divest
[13, 17, 18, 19, 20, 21]

Unapproved

7.88.x

Unapproved

Approved w/Constraints
[13, 15, 16, 17]

Divest
[13, 17, 18, 19, 20, 21]

8.4.x

Unapproved

Approved w/Constraints
[13, 17, 18, 19, 20, 21]

Decision Constraints


[1]	Note: the utility must remain properly patched in order to mitigate known or future security vulnerabilities. If using v24 please refer to CVE-2012-0036 for known vulnerabilities. If using v21 and below please refer to CVE-2011-2192 and CVE-2010-3842 for known vulnerabilities.

[2]	Due to multiple NIST security vulnerabilities, extra vigilance should be applied to ensure the product remains properly patched to mitigate known and future vulnerabilities. Product must be operated in accordance with Federal and Department security and privacy policies and guidelines. The product supports network protocols currently unapproved or prohibited including FTP and NTLMv1 respectively. Use of this product must comply with organization network protocol constraints.

[3]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[4]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[5]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[6]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[7]	This product is compatible with File Transfer Protocol (FTP) which is unapproved in the TRM. Users must avoid using functionalities for this product that leverage FTP. Versions 7.1x.x and 7.2x.x of cURL are only approved for use with the associated Red Hat Enterprise Linux (RHEL) versions 6.x and 7.x they are included and supported with. All other applications of this technology must use cURL version 7.5x.x or later.

[8]	This product is compatible with File Transfer Protocol (FTP) which is unapproved in the TRM. Users must avoid using functionalities for this product that leverage FTP.

[9]	This product is compatible with File Transfer Protocol (FTP) which is unapproved in the TRM. Users must avoid using functionalities for this product that leverage FTP. Per the Initial Product Review, users must abide by the following constraints: VA personnel using cURL must use version 7.68 or higher. Additionally, developers must insure secure coding practices are used such as proper bounds checks and input validation.

[10]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[11]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[12]	This product is compatible with File Transfer Protocol (FTP) which is unapproved in the TRM. Users must avoid using functionalities for this product that leverage FTP. Per the Initial Product Review, users must abide by the following constraints: VA personnel using cURL must use the recent stable version. Additionally, developers must insure secure coding practices are used such as proper bounds checks and input validation. This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.

[13]	This technology has received one or more VA security bulletins that provide specific guidance on vulnerability patching and mitigation. It is the responsibility of VA system owners to ensure that the appropriate mitigations are taken to address all known and future discovered vulnerabilities with this product. See the Reference tab for more information on security bulletins related to this product.

[14]	This product is compatible with File Transfer Protocol (FTP) which is unapproved in the TRM. Users must avoid using functionalities for this product that leverage FTP. Per the Initial Product Review, users must abide by the following constraints: VA personnel using cURL must use the recent stable version. Additionally, developers must insure secure coding practices are used such as proper bounds checks and input validation. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.

[15]	This product is compatible with File Transfer Protocol (FTP) which is unapproved in the TRM. Users must avoid using functionalities for this product that leverage FTP. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Per the Initial Product Review, users must abide by the following constraints: VA personnel using cURL must use the recent stable version. Additionally, developers must insure secure coding practices are used such as proper bounds checks and input validation.

[16]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[17]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[18]	This product is compatible with File Transfer Protocol (FTP) which is unapproved in the TRM. Users must avoid using functionalities for this product that leverage FTP. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM. Per the Initial Product Review, users must abide by the following constraints: VA personnel using cURL must use the most recent, VA approved, stable version. System owners should monitor both the CVE Details and NIST National Vulnerability Database websites for any new security vulnerabilities. cURL will require a 3rd party FIPS 140-2 certified solution for any data containing PHI/PII or VA sensitive information. Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[19]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[20]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[21]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

Note:

At the time of writing, version 8.4.0 is the most current version, released 10/11/2023.

References

The following reference(s) are associated with this entry:
Type	Name	Description
Vendor Provided*	cURL Manual	This document repository offers users basic instructions on how to utilize the cURL software.
Vendor Provided*	Version History	Client for URLs version history updates.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
libcurl - the multiprotocol file transfer library	libcurl is a free and easy-to-use client-side URL transfer library, supporting DICT, FILE, FTP, FTPS, Gopher, HTTP, HTTPS, IMAP, IMAPS, LDAP, LDAPS, POP3, POP3S, RTMP, RTSP, SCP, SFTP, SMTP, SMTPS, Telnet and TFTP. libcurl supports SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form based upload, proxies, cookies, user+password authentication (Basic, Digest, NTLM, Negotiate, Kerberos), file transfer resume, http proxy tunneling and more

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Miscellaneous Productivity Tools and Utilities

Open Source

This entry is available as an open source technology.

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Red Hat Enterprise Linux (RHEL) - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

No runtime dependencies have been identified.

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology may improve productivity for specific staff whose responsibilities include transferring data across platforms via command line.
This technology is available at no cost through open-source licensing and supports VA`s open source initiative.
This technology has a comprehensive set of documentation.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this technology. Please see https://nvd.NIST.gov/vuln/search for more details.
cURL provides a list of known security vulnerabilities on their webpage. There are multiple published vulnerabilities ranging from buffer overflows to disclosure of credentials.
cURL is not Federal Information Processing standards (FIPS) 140-2 certified.
cURL is free opensource software.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
This technology can potentially use File Transfer Protocol (FTP), an unapproved protocol.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this technology.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
This technology can potentially use Secure Sockets Layer (SSL), an unapproved protocol.
There is no indication based on available vendor documentation that this technology is Federal Information Processing Standard (FIPS) 140-2 compliant.
As open-source software, this product may be left without clearly defined support options which may result in suboptimal enterprise level support.

Architectural Benefits

This technology is portable as it runs on multiple TRM-approved operating systems.
This technology is compatible with multiple other Technical Reference Model (TRM) technologies and standards used by the organization.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (11/09/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (11/09/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

EMAIL UPDATES