CVE-2019-17659 (GCVE-0-2019-17659)
Vulnerability from cvelistv5
Published
2025-03-17 13:06
Modified
2025-03-17 13:35
Severity ?
VLAI Severity ?
EPSS score ?
CWE
- CWE-798 - Improper access control
Summary
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.
References
{
"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"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…