{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5137 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5137 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5137 is a high-severity vulnerability in Moxa, published on 25 Feb 2020. 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-5137 and fix it if it is affected.\n\nWhat it is: CVE-2019-5137 is a high-severity vulnerability in Moxa, published on 25 Feb 2020. 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-5137 in the wild and no public exploit code.\n\nAffected product: Moxa. 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-5137/ (Markdown: https://insights.sbomify.com/CVE-2019-5137/index.md)","id":"CVE-2019-5137","markdown":"https://insights.sbomify.com/CVE-2019-5137/index.md","name":"CVE-2019-5137","record":{"aliases":["GHSA-2v7g-r6qx-cv4h"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Moxa wireless access point","requires_auth":"none","summary":"Hard-coded cryptographic keys in the ServiceAgent binary allow attackers to decrypt network traffic on Moxa AWK-3131A devices.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"awk-3131a_firmware","vendor":"moxa"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"The usage of hard-coded cryptographic keys within the ServiceAgent binary allows for the decryption of captured traffic across the network from or to the Moxa AWK-3131A firmware version 1.13.","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 Moxa","id":"CVE-2019-5137","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Moxa","id":"CVE-2019-5138"},"packages":[],"prev":{"headline":"Privilege escalation in Moxa","id":"CVE-2019-5136"},"products":["Moxa"],"published":"2020-02-25","related":[{"cvss_score":10,"headline":"Command injection in Moxa","id":"CVE-2017-14459","kev_date_added":null,"published":"2018-04-11"},{"cvss_score":10,"headline":"Hardcoded credentials in Moxa","id":"CVE-2016-8717","kev_date_added":null,"published":"2018-04-02"},{"cvss_score":9.9,"headline":"Command injection in Moxa","id":"CVE-2019-5138","kev_date_added":null,"published":"2020-02-25"},{"cvss_score":9.9,"headline":"Memory corruption in Moxa","id":"CVE-2019-5153","kev_date_added":null,"published":"2020-02-25"},{"cvss_score":9.9,"headline":"Missing authorization in Moxa","id":"CVE-2019-5162","kev_date_added":null,"published":"2020-02-25"},{"cvss_score":9.1,"headline":"Command injection in Moxa AWK-3131A WAP","id":"CVE-2016-8721","kev_date_added":null,"published":"2017-04-20"},{"cvss_score":8.8,"headline":"Privilege escalation in Moxa","id":"CVE-2019-5136","kev_date_added":null,"published":"2020-02-25"}],"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-04","vendors":["n/a"]},"summary":"Hard-coded cryptographic keys in the ServiceAgent binary allow attackers to decrypt network traffic on Moxa AWK-3131A devices.","url":"https://insights.sbomify.com/CVE-2019-5137/"}