{"answers":{"affected":"It affects 9 products.","exploited":"There is no known exploitation of CVE-2019-15802 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15802 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15802 is a medium-severity vulnerability in n/a, published on 14 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15802 and fix it if it is affected.\n\nWhat it is: CVE-2019-15802 is a medium-severity vulnerability in n/a, published on 14 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-15802 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-15802/ (Markdown: https://insights.sbomify.com/CVE-2019-15802/index.md)","id":"CVE-2019-15802","markdown":"https://insights.sbomify.com/CVE-2019-15802/index.md","name":"CVE-2019-15802","record":{"aliases":["GHSA-fmpq-8rp4-f234"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Zyxel network switch","requires_auth":"none","summary":"Attackers can decrypt stored passwords using a hardcoded key, exposing credentials from configuration backups and firmware on Zyxel switches.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"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":5.9,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered on Zyxel GS1900 devices with firmware before 2.50(AAHH.0)C0. The firmware hashes and encrypts passwords using a hardcoded cryptographic key in sal_util_str_encrypt() in libsal.so.0.0. The parameters (salt, IV, and key data) are used to encrypt and decrypt all passwords using AES256 in CBC mode. With the parameters known, all previously encrypted passwords can be decrypted. This includes the passwords that are part of configuration backups or otherwise embedded as part of the firmware.","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":"Hardcoded credentials in n/a","id":"CVE-2019-15802","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-15803"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2019-15801"},"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":"Privilege escalation in n/a","id":"CVE-2019-15799","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":"Attackers can decrypt stored passwords using a hardcoded key, exposing credentials from configuration backups and firmware on Zyxel switches.","url":"https://insights.sbomify.com/CVE-2019-15802/"}