{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34045 exists.","fix":"No fix has been published for CVE-2022-34045 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34045 is a critical vulnerability in n/a, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34045 and fix it if it is affected.\n\nWhat it is: CVE-2022-34045 is a critical vulnerability in n/a, published on 20 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-34045 exists.\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-2022-34045/ (Markdown: https://insights.sbomify.com/CVE-2022-34045/index.md)","id":"CVE-2022-34045","markdown":"https://insights.sbomify.com/CVE-2022-34045/index.md","name":"CVE-2022-34045","record":{"aliases":["GHSA-4pgr-vxfc-4wm7"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wavlink router","requires_auth":"none","summary":"Attackers can decrypt configuration files using a hardcoded key, exposing sensitive settings on Wavlink routers.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wl-wn530hg4_firmware","vendor":"wavlink"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Wavlink WN530HG4 M30HG4.V5030.191116 was discovered to contain a hardcoded encryption/decryption key for its configuration files at /etc_ro/lighttpd/www/cgi-bin/ExportAllSettings.sh.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-34045.yaml","stars":null,"title":"WAVLINK WN530HG4 - Improper Access Control"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-34045","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-34046"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2022-34043"},"products":["n/a"],"published":"2022-07-20","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-15489","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-15490","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-10971","kev_date_added":null,"published":"2020-05-07"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2022-48166","kev_date_added":null,"published":"2023-02-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-34047","kev_date_added":null,"published":"2022-07-20"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2022-34049","kev_date_added":null,"published":"2022-07-20"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can decrypt configuration files using a hardcoded key, exposing sensitive settings on Wavlink routers.","url":"https://insights.sbomify.com/CVE-2022-34045/"}