{"answers":{"affected":"It affects 9 products.","exploited":"There is no known exploitation of CVE-2019-15799 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15799 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15799 is a high-severity vulnerability in n/a, published on 14 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15799 and fix it if it is affected.\n\nWhat it is: CVE-2019-15799 is a high-severity vulnerability in n/a, published on 14 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-15799 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-15799/ (Markdown: https://insights.sbomify.com/CVE-2019-15799/index.md)","id":"CVE-2019-15799","markdown":"https://insights.sbomify.com/CVE-2019-15799/index.md","name":"CVE-2019-15799","record":{"aliases":["GHSA-fvpf-4m7h-jg3p"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Zyxel managed switch","requires_auth":"low_privilege","summary":"Low-privilege SSH users can retrieve and decrypt admin passwords via tech-support command, leading to full administrative access on Zyxel switches.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gs1900-10hp_firmware","vendor":"zyxel"},{"product":"gs1900-16_firmware","vendor":"zyxel"},{"product":"gs1900-24_firmware","vendor":"zyxel"},{"product":"gs1900-24e_firmware","vendor":"zyxel"},{"product":"gs1900-24hp_firmware","vendor":"zyxel"},{"product":"gs1900-48_firmware","vendor":"zyxel"},{"product":"gs1900-48hp_firmware","vendor":"zyxel"},{"product":"gs1900-8_firmware","vendor":"zyxel"},{"product":"gs1900-8hp_firmware","vendor":"zyxel"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"An issue was discovered on Zyxel GS1900 devices with firmware before 2.50(AAHH.0)C0. User accounts created through the web interface of the device, when given non-admin level privileges, have the same level of privileged access as administrators when connecting to the device via SSH (while their permissions via the web interface are in fact restricted). This allows normal users to obtain the administrative password by running the tech-support command via the CLI: this contains the encrypted passwords for all users on the device. As these passwords are encrypted using well-known and static parameters, they can be decrypted and the original passwords (including the administrator password) can be obtained.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2019-15799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2019-15800"},"packages":[],"prev":{"headline":"CVE ID was once reserved, but never used.","id":"CVE-2019-15798"},"products":["n/a"],"published":"2019-11-14","related":[{"cvss_score":8.8,"headline":"Zyxel GS1900 Series Switches Stack-Based Buffer Overflow","id":"CVE-2026-7273","kev_date_added":"2026-09-21","published":"2026-06-16"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-15800","kev_date_added":null,"published":"2019-11-14"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2015-5988","kev_date_added":null,"published":"2015-12-31"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2015-5989","kev_date_added":null,"published":"2015-12-31"},{"cvss_score":9.1,"headline":"Auth bypass in n/a","id":"CVE-2019-15803","kev_date_added":null,"published":"2019-11-14"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2015-5990","kev_date_added":null,"published":"2015-12-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Low-privilege SSH users can retrieve and decrypt admin passwords via tech-support command, leading to full administrative access on Zyxel switches.","url":"https://insights.sbomify.com/CVE-2019-15799/"}