CVE-2016-3083 (GCVE-0-2016-3083)
Vulnerability from cvelistv5 – Published: 2017-05-30 14:00 – Updated: 2024-08-05 23:40- Information Disclosure
| URL | Tags |
|---|---|
| https://lists.apache.org/thread.html/0851bcf85635… | mailing-listx_refsource_MLIST |
| http://www.securityfocus.com/bid/98669 | vdb-entryx_refsource_BID |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Apache Software Foundation | Apache Hive |
Affected:
0.11.0 - 0.14.0
Affected: 1.0.0 - 1.2.1 Affected: 2.0.0 |
guessed |
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-05T23:40:15.584Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"name": "[dev] 20170524 CVE-2016-3083: Apache Hive SSL vulnerability bug disclosure",
"tags": [
"mailing-list",
"x_refsource_MLIST",
"x_transferred"
],
"url": "https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E"
},
{
"name": "98669",
"tags": [
"vdb-entry",
"x_refsource_BID",
"x_transferred"
],
"url": "http://www.securityfocus.com/bid/98669"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"product": "Apache Hive",
"vendor": "Apache Software Foundation",
"versions": [
{
"status": "affected",
"version": "0.11.0 - 0.14.0"
},
{
"status": "affected",
"version": "1.0.0 - 1.2.1"
},
{
"status": "affected",
"version": "2.0.0"
}
]
}
],
"datePublic": "2017-05-24T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "Apache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server\u0027s certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn\u0027t seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through."
}
],
"problemTypes": [
{
"descriptions": [
{
"description": "Information Disclosure",
"lang": "en",
"type": "text"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2017-05-31T09:57:01.000Z",
"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
"shortName": "apache"
},
"references": [
{
"name": "[dev] 20170524 CVE-2016-3083: Apache Hive SSL vulnerability bug disclosure",
"tags": [
"mailing-list",
"x_refsource_MLIST"
],
"url": "https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E"
},
{
"name": "98669",
"tags": [
"vdb-entry",
"x_refsource_BID"
],
"url": "http://www.securityfocus.com/bid/98669"
}
],
"x_legacyV4Record": {
"CVE_data_meta": {
"ASSIGNER": "security@apache.org",
"ID": "CVE-2016-3083",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "Apache Hive",
"version": {
"version_data": [
{
"version_value": "0.11.0 - 0.14.0"
},
{
"version_value": "1.0.0 - 1.2.1"
},
{
"version_value": "2.0.0"
}
]
}
}
]
},
"vendor_name": "Apache Software Foundation"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "Apache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server\u0027s certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn\u0027t seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "Information Disclosure"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "[dev] 20170524 CVE-2016-3083: Apache Hive SSL vulnerability bug disclosure",
"refsource": "MLIST",
"url": "https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192@%3Cdev.hive.apache.org%3E"
},
{
"name": "98669",
"refsource": "BID",
"url": "http://www.securityfocus.com/bid/98669"
}
]
}
}
}
},
"cveMetadata": {
"assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
"assignerShortName": "apache",
"cveId": "CVE-2016-3083",
"datePublished": "2017-05-30T14:00:00.000Z",
"dateReserved": "2016-03-10T00:00:00.000Z",
"dateUpdated": "2024-08-05T23:40:15.584Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2016-3083",
"date": "2026-10-28",
"epss": "0.01006",
"percentile": "0.62876"
},
"fkie_nvd": {
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:apache:hive:0.13.0:*:*:*:*:*:*:*",
"matchCriteriaId": "4BE36554-0C96-406E-80EB-ECDB0E1CA2D6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:0.13.1:*:*:*:*:*:*:*",
"matchCriteriaId": "39667946-AA1C-4CCF-B22F-431A24102A79",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:0.14.0:*:*:*:*:*:*:*",
"matchCriteriaId": "83A48669-26C6-490D-9686-51A2BED1FB29",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "9EFCB996-0ED9-4FFC-BB76-8742306D47B9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.0.1:*:*:*:*:*:*:*",
"matchCriteriaId": "650C90FA-1D6C-4015-A92B-9852D6CEA2F7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "0139B115-DD15-4C84-ACA9-1F0426496288",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.1.1:*:*:*:*:*:*:*",
"matchCriteriaId": "7C363DD3-BB9E-4AE2-9C81-731043E80858",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.2.0:*:*:*:*:*:*:*",
"matchCriteriaId": "472BB9D5-CE7A-4E14-A8F2-349AE2982B93",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.2.1:*:*:*:*:*:*:*",
"matchCriteriaId": "C4554B70-61AB-4E00-92EE-FFD462B2D953",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Apache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server\u0027s certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn\u0027t seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through."
},
{
"lang": "es",
"value": "Apache Hive (JDBC + HiveServer2) implementa SSL para conexiones planas TCP y HTTP (soporta ambos modos de transporte). Mientras se comprueba el certificado del servidor durante la configuraci\u00f3n de la conexi\u00f3n, el cliente Apache Hive anterior a versi\u00f3n 1.2.2 y versiones 2.0.x anteriores a 2.0.1, no parece estar comprobando el atributo de nombre com\u00fan del certificado. De este modo, si un cliente JDBC env\u00eda una petici\u00f3n SSL al servidor abc.com y el servidor responde con un certificado v\u00e1lido (certificado por CA) pero emitido a xyz.com, el cliente lo aceptar\u00e1 como certificado v\u00e1lido y el protocolo de enlace SSL pasar\u00e1."
}
],
"id": "CVE-2016-3083",
"lastModified": "2024-11-21T02:49:19.790",
"metrics": {
"cvssMetricV2": [
{
"acInsufInfo": false,
"baseSeverity": "MEDIUM",
"cvssData": {
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"availabilityImpact": "NONE",
"baseScore": 5.0,
"confidentialityImpact": "NONE",
"integrityImpact": "PARTIAL",
"vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
"version": "2.0"
},
"exploitabilityScore": 10.0,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"source": "nvd@nist.gov",
"type": "Primary",
"userInteractionRequired": false
}
],
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"version": "3.0"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2017-05-30T14:29:00.207",
"references": [
{
"source": "security@apache.org",
"url": "http://www.securityfocus.com/bid/98669"
},
{
"source": "security@apache.org",
"url": "https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "http://www.securityfocus.com/bid/98669"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E"
}
],
"sourceIdentifier": "security@apache.org",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-295"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"nvd": {
"cve": {
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:apache:hive:0.13.0:*:*:*:*:*:*:*",
"matchCriteriaId": "4BE36554-0C96-406E-80EB-ECDB0E1CA2D6",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:0.13.1:*:*:*:*:*:*:*",
"matchCriteriaId": "39667946-AA1C-4CCF-B22F-431A24102A79",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:0.14.0:*:*:*:*:*:*:*",
"matchCriteriaId": "83A48669-26C6-490D-9686-51A2BED1FB29",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.0.0:*:*:*:*:*:*:*",
"matchCriteriaId": "9EFCB996-0ED9-4FFC-BB76-8742306D47B9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.0.1:*:*:*:*:*:*:*",
"matchCriteriaId": "650C90FA-1D6C-4015-A92B-9852D6CEA2F7",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.1.0:*:*:*:*:*:*:*",
"matchCriteriaId": "0139B115-DD15-4C84-ACA9-1F0426496288",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.1.1:*:*:*:*:*:*:*",
"matchCriteriaId": "7C363DD3-BB9E-4AE2-9C81-731043E80858",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.2.0:*:*:*:*:*:*:*",
"matchCriteriaId": "472BB9D5-CE7A-4E14-A8F2-349AE2982B93",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:hive:1.2.1:*:*:*:*:*:*:*",
"matchCriteriaId": "C4554B70-61AB-4E00-92EE-FFD462B2D953",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Apache Hive (JDBC + HiveServer2) implements SSL for plain TCP and HTTP connections (it supports both transport modes). While validating the server\u0027s certificate during the connection setup, the client in Apache Hive before 1.2.2 and 2.0.x before 2.0.1 doesn\u0027t seem to be verifying the common name attribute of the certificate. In this way, if a JDBC client sends an SSL request to server abc.com, and the server responds with a valid certificate (certified by CA) but issued to xyz.com, the client will accept that as a valid certificate and the SSL handshake will go through."
},
{
"lang": "es",
"value": "Apache Hive (JDBC + HiveServer2) implementa SSL para conexiones planas TCP y HTTP (soporta ambos modos de transporte). Mientras se comprueba el certificado del servidor durante la configuraci\u00f3n de la conexi\u00f3n, el cliente Apache Hive anterior a versi\u00f3n 1.2.2 y versiones 2.0.x anteriores a 2.0.1, no parece estar comprobando el atributo de nombre com\u00fan del certificado. De este modo, si un cliente JDBC env\u00eda una petici\u00f3n SSL al servidor abc.com y el servidor responde con un certificado v\u00e1lido (certificado por CA) pero emitido a xyz.com, el cliente lo aceptar\u00e1 como certificado v\u00e1lido y el protocolo de enlace SSL pasar\u00e1."
}
],
"id": "CVE-2016-3083",
"lastModified": "2026-05-13T00:24:29.033",
"metrics": {
"cvssMetricV2": [
{
"acInsufInfo": false,
"baseSeverity": "MEDIUM",
"cvssData": {
"accessComplexity": "LOW",
"accessVector": "NETWORK",
"authentication": "NONE",
"availabilityImpact": "NONE",
"baseScore": 5.0,
"confidentialityImpact": "NONE",
"integrityImpact": "PARTIAL",
"vectorString": "AV:N/AC:L/Au:N/C:N/I:P/A:N",
"version": "2.0"
},
"exploitabilityScore": 10.0,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"source": "nvd@nist.gov",
"type": "Primary",
"userInteractionRequired": false
}
],
"cvssMetricV30": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
"version": "3.0"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2017-05-30T14:29:00.207",
"references": [
{
"source": "security@apache.org",
"url": "http://www.securityfocus.com/bid/98669"
},
{
"source": "security@apache.org",
"url": "https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "http://www.securityfocus.com/bid/98669"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"url": "https://lists.apache.org/thread.html/0851bcf85635385f94cdaa008053802d92b4aab0a3075e30ed171192%40%3Cdev.hive.apache.org%3E"
}
],
"sourceIdentifier": "security@apache.org",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-295"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
},
"redhat_vex": {
"current_release_date": "2025-11-21T17:16:22+00:00",
"cve": "CVE-2016-3083",
"id": "CVE-2016-3083",
"initial_release_date": "2016-01-01T00:00:00+00:00",
"product_status:known_not_affected": "1",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "hive: Common name attribute of the certificate is not verified",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2016/cve-2016-3083.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.