not verifying certs for TLS to IP address / Secure Transport
When asked to do a TLS connection (HTTPS, FTPS, IMAPS, etc) to a URL specified with an IP address instead of a name, libcurl would wrongly not verify the server's name in the certificate. The signature (whether it was signed by a trusted CA) and validity (whether the date was within the certificate's lifetime and it was not revoked) verification was still performed. This is a problem in libcurl built to use the Secure Transport backend. Secure Transport is the TLS library present and used on Mac OS X and iOS. Only users on Mac OS X or iOS can be affected by this, and only if libcurl was built to use the native TLS backend library. This problem was initially used as an example of the Apple SSL bug that hit [the news in late February 2014](https://www.imperialviolet.org/2014/02/22/applebug.html) but that was not correct.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2014-1263
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 14:10 UTC · Revision 1
Source evidence
not verifying certs for TLS to IP address / Secure Transport
core-osv · Original sourcePublished 26 Mar 2014, 08:00 UTC
When asked to do a TLS connection (HTTPS, FTPS, IMAPS, etc) to a URL specified with an IP address instead of a name, libcurl would wrongly not verify the server's name in the certificate. The signature (whether it was signed by a trusted CA) and validity (whether the date was within the certificate's lifetime and it was not revoked) verification was still performed. This is a problem in libcurl built to use the Secure Transport backend. Secure Transport is the TLS library present and used on Mac OS X and iOS. Only users on Mac OS X or iOS can be affected by this, and only if libcurl was built to use the native TLS backend library. This problem was initially used as an example of the Apple SSL bug that hit [the news in late February 2014](https://www.imperialviolet.org/2014/02/22/applebug.html) but that was not correct.
osv:CURL-CVE-2014-1263
Complete source record
{
"id": "209236b023049d0737b0139e3193b8e25e3564cbbf1773b5d2e71593b1af29b8",
"url": "https://osv.dev/vulnerability/CURL-CVE-2014-1263",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "not verifying certs for TLS to IP address / Secure Transport",
"summary": "When asked to do a TLS connection (HTTPS, FTPS, IMAPS, etc) to a URL specified with an IP address instead of a name, libcurl would wrongly not verify the server's name in the certificate. The signature (whether it was signed by a trusted CA) and validity (whether the date was within the certificate's lifetime and it was not revoked) verification was still performed. This is a problem in libcurl built to use the Secure Transport backend. Secure Transport is the TLS library present and used on Mac OS X and iOS. Only users on Mac OS X or iOS can be affected by this, and only if libcurl was built to use the native TLS backend library. This problem was initially used as an example of the Apple SSL bug that hit [the news in late February 2014](https://www.imperialviolet.org/2014/02/22/applebug.html) but that was not correct.",
"evidence": "osv:CURL-CVE-2014-1263",
"products": [],
"severity": "medium",
"structured": {
"id": "CURL-CVE-2014-1263",
"aliases": [
"CURL-CVE-2014-1263",
"CVE-2014-1263"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "7.27.0"
},
{
"fixed": "7.36.0"
}
]
},
{
"repo": "https://github.com/curl/curl.git",
"type": "GIT",
"events": [
{
"introduced": "6d1ea388cbd9de7f2a944a0c64f5feaec1b1904a"
},
{
"fixed": "afc6e5004fabee590e41ffe750a237e1187fbbbd"
}
]
}
],
"versions": [
"7.35.0",
"7.34.0",
"7.33.0",
"7.32.0",
"7.31.0",
"7.30.0",
"7.29.0",
"7.28.1",
"7.28.0",
"7.27.0",
"curl-7_35_0",
"curl-7_34_0",
"curl-7_33_0",
"curl-7_32_0",
"curl-7_31_0",
"curl-7_30_0",
"curl-7_29_0",
"curl-7_28_1",
"curl-7_28_0",
"curl-7_27_0"
],
"database_specific": {
"source": "https://curl.se/docs/CURL-CVE-2014-1263.json",
"vanir_signatures": [
{
"id": "CURL-CVE-2014-1263-46deb206",
"digest": {
"length": 12664,
"function_hash": "118892292214048643035672840983136210857"
},
"source": "https://github.com/curl/curl.git/commit/afc6e5004fabee590e41ffe750a237e1187fbbbd",
"target": {
"file": "lib/vtls/curl_darwinssl.c",
"function": "darwinssl_connect_step1"
},
"deprecated": false,
"signature_type": "Function",
"signature_version": "v1"
},
{
"id": "CURL-CVE-2014-1263-8945bbe3",
"digest": {
"threshold": 0.9,
"line_hashes": [
"316255875844261537459574858674279425871",
"239378137043493369965312323354307456067",
"204640828372644162492254219113765752460",
"219459843959473681948300350369099033059",
"58683795751729623030046900533268359601",
"68010053885667392452433109099392771147",
"326748351302449136049322361015970921228",
"244996404508351932339435100811283724032",
"208098070630273559268760496294166926428",
"131374684106720825121641423745765234123",
"264295880985067059370503250389482572375",
"316499748253954725996549419519249869439",
"304252583710625668890348546343893798971",
"319139195181975568023432909836975337027"
]
},
"source": "https://github.com/curl/curl.git/commit/afc6e5004fabee590e41ffe750a237e1187fbbbd",
"target": {
"file": "lib/vtls/curl_darwinssl.c"
},
"deprecated": false,
"signature_type": "Line",
"signature_version": "v1"
}
],
"vanir_signatures_modified": "2026-10-26T13:07:53Z"
}
}
],
"modified": "2026-10-26T13:07:53.733842486Z",
"provider": "osv",
"references": [],
"provider_metadata": {
"CWE": {
"id": "CWE-297",
"desc": "Improper Validation of Certificate with Host Mismatch"
},
"URL": "https://curl.se/docs/CVE-2014-1263.json",
"www": "https://curl.se/docs/CVE-2014-1263.html",
"affects": "both",
"package": "curl",
"severity": "Medium",
"last_affected": "7.35.0"
}
},
"related_cves": [
{
"value": "CVE-2014-1263",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 453274,
"published_at": "2014-03-26T08:00:00+00:00"
}