CVE-2019-17659 (GCVE-0-2019-17659)
Vulnerability from cvelistv5 – Published: 2025-03-17 13:06 – Updated: 2025-03-17 13:35- CWE-798 - Improper access control
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2019-17659",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-03-17T13:35:01.135210Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-03-17T13:35:08.816Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [],
"defaultStatus": "unaffected",
"product": "FortiSIEM",
"vendor": "Fortinet",
"versions": [
{
"status": "affected",
"version": "5.2.6"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "A use of hard-coded cryptographic key vulnerability in FortiSIEM version 5.2.6 may allow a remote unauthenticated attacker to obtain SSH access to the supervisor as the restricted user \"tunneluser\" by leveraging knowledge of the private key from another installation or a firmware image."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 3.6,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L/E:F/RL:X/RC:X",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-798",
"description": "Improper access control",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-03-17T13:06:07.828Z",
"orgId": "6abe59d8-c742-4dff-8ce8-9b0ca1073da8",
"shortName": "fortinet"
},
"references": [
{
"name": "https://fortiguard.fortinet.com/psirt/FG-IR-19-296",
"url": "https://fortiguard.fortinet.com/psirt/FG-IR-19-296"
}
],
"solutions": [
{
"lang": "en",
"value": "Please upgrade to FortiSIEM version 5.2.7 and above where this issue is resolved. \r\nWorkaround (for FortiSIEM version 5.2.6 and lower): \r\nCustomers who are not using the reverse tunnel feature are advised to disable SSH service on port 19999 by following the steps below :\r\n1. SSH to the Supervisor node as the root user.\r\n2. Remove tunneluser SSH configuration file to disable listening on port 19999:\r\nrm -f /etc/ssh/sshd_config.tunneluser\r\necho rm -f /etc/ssh/sshd_config.tunneluser \u003e\u003e /etc/init.d/phProvision.sh\r\n3. Then terminate sshd running on TCP Port 19999 as follows:\r\npkill -f /usr/sbin/sshd -p 19999\r\n4.Additional steps can be performed on Supervisor to remove the keys associated with tunneluser account:\r\nrm -f /opt/phoenix/deployment/id_rsa.pub.tunneluser\r\nrm -f /home/tunneluser/.ssh/authorized_keys\r\nrm -f /opt/phoenix/id_rsa.tunneluser ~admin/.ssh/id_rsa\r\nCustomers are also advised to disable \"tunneluser\" SSH access on port 22 by following the steps bwlow:\r\n1. SSH to the Supervisor node as the root user.\r\n2. Add/edit the following line in sshd_config file: \r\necho DenyUsers tunneluser \u003e\u003e /etc/ssh/sshd_config\r\n3. service sshd restart"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "6abe59d8-c742-4dff-8ce8-9b0ca1073da8",
"assignerShortName": "fortinet",
"cveId": "CVE-2019-17659",
"datePublished": "2025-03-17T13:06:07.828Z",
"dateReserved": "2019-10-16T00:00:00.000Z",
"dateUpdated": "2025-03-17T13:35:08.816Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2019-17659",
"date": "2026-11-16",
"epss": "0.00652",
"percentile": "0.51826"
},
"nvd": {
"cve": {
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:fortinet:fortisiem:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C961C610-69DC-495B-BEA0-203F0A2AD0C1",
"versionEndExcluding": "5.2.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "A use of hard-coded cryptographic key vulnerability in FortiSIEM version 5.2.6 may allow a remote unauthenticated attacker to obtain SSH access to the supervisor as the restricted user \"tunneluser\" by leveraging knowledge of the private key from another installation or a firmware image."
},
{
"lang": "es",
"value": "Una vulnerabilidad en el uso de una clave criptogr\u00e1fica codificada en FortiSIEM versi\u00f3n 5.2.6 puede permitir que un atacante remoto no autenticado obtenga acceso SSH al supervisor como el usuario restringido \"tunneluser\" aprovechando el conocimiento de la clave privada de otra instalaci\u00f3n o una imagen de firmware."
}
],
"id": "CVE-2019-17659",
"lastModified": "2025-07-15T16:48:48.100",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 3.7,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 1.4,
"source": "psirt@fortinet.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
]
},
"published": "2025-03-17T14:15:16.360",
"references": [
{
"source": "psirt@fortinet.com",
"tags": [
"Vendor Advisory"
],
"url": "https://fortiguard.fortinet.com/psirt/FG-IR-19-296"
}
],
"sourceIdentifier": "psirt@fortinet.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-798"
}
],
"source": "psirt@fortinet.com",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2019-17659",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-03-17T13:35:01.135210Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-03-17T13:35:04.552Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"cpes": [],
"defaultStatus": "unaffected",
"product": "FortiSIEM",
"vendor": "Fortinet",
"versions": [
{
"status": "affected",
"version": "5.2.6"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "A use of hard-coded cryptographic key vulnerability in FortiSIEM version 5.2.6 may allow a remote unauthenticated attacker to obtain SSH access to the supervisor as the restricted user \"tunneluser\" by leveraging knowledge of the private key from another installation or a firmware image."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 3.6,
"baseSeverity": "LOW",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L/E:F/RL:X/RC:X",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-798",
"description": "Improper access control",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-03-17T13:06:07.828Z",
"orgId": "6abe59d8-c742-4dff-8ce8-9b0ca1073da8",
"shortName": "fortinet"
},
"references": [
{
"name": "https://fortiguard.fortinet.com/psirt/FG-IR-19-296",
"url": "https://fortiguard.fortinet.com/psirt/FG-IR-19-296"
}
],
"solutions": [
{
"lang": "en",
"value": "Please upgrade to FortiSIEM version 5.2.7 and above where this issue is resolved. \r\nWorkaround (for FortiSIEM version 5.2.6 and lower): \r\nCustomers who are not using the reverse tunnel feature are advised to disable SSH service on port 19999 by following the steps below :\r\n1. SSH to the Supervisor node as the root user.\r\n2. Remove tunneluser SSH configuration file to disable listening on port 19999:\r\nrm -f /etc/ssh/sshd_config.tunneluser\r\necho rm -f /etc/ssh/sshd_config.tunneluser \u003e\u003e /etc/init.d/phProvision.sh\r\n3. Then terminate sshd running on TCP Port 19999 as follows:\r\npkill -f /usr/sbin/sshd -p 19999\r\n4.Additional steps can be performed on Supervisor to remove the keys associated with tunneluser account:\r\nrm -f /opt/phoenix/deployment/id_rsa.pub.tunneluser\r\nrm -f /home/tunneluser/.ssh/authorized_keys\r\nrm -f /opt/phoenix/id_rsa.tunneluser ~admin/.ssh/id_rsa\r\nCustomers are also advised to disable \"tunneluser\" SSH access on port 22 by following the steps bwlow:\r\n1. SSH to the Supervisor node as the root user.\r\n2. Add/edit the following line in sshd_config file: \r\necho DenyUsers tunneluser \u003e\u003e /etc/ssh/sshd_config\r\n3. service sshd restart"
}
]
}
},
"cveMetadata": {
"assignerOrgId": "6abe59d8-c742-4dff-8ce8-9b0ca1073da8",
"assignerShortName": "fortinet",
"cveId": "CVE-2019-17659",
"datePublished": "2025-03-17T13:06:07.828Z",
"dateReserved": "2019-10-16T00:00:00.000Z",
"dateUpdated": "2025-03-17T13:35:08.816Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
}
}
Solutions
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.