{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30623 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30623 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30623 is a medium-severity authentication bypass vulnerability in Chcnav - P5E GNSS, published on 18 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-30623 and fix it if it is affected.\n\nWhat it is: CVE-2022-30623 is a medium-severity authentication bypass vulnerability in Chcnav - P5E GNSS, published on 18 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-30623 in the wild and no public exploit code.\n\nAffected product: Chcnav - P5E GNSS. 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-30623/ (Markdown: https://insights.sbomify.com/CVE-2022-30623/index.md)","id":"CVE-2022-30623","markdown":"https://insights.sbomify.com/CVE-2022-30623/index.md","name":"CVE-2022-30623","record":{"aliases":["GHSA-5mcf-4jxx-fhq7"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GNSS receiver","requires_auth":"none","summary":"Attackers can bypass authentication on Chcnav P5E GNSS devices by manipulating a specific cookie value, gaining unauthorized access to the system.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCD","cpe":[{"product":"p5e_gnss_firmware","vendor":"chcnav"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"The server checks the user's cookie in a non-standard way, and a value is entered in the cookie value name of the status and its value is set to true to bypass the identification with the system using a username and password.","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":"Chcnav - P5E GNSS Authentication bypass","id":"CVE-2022-30623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Chcnav - P5E GNSS Authentication bypass admin password reset","id":"CVE-2022-30624"},"packages":[],"prev":{"headline":"Chcnav - P5E GNSS Information disclosure","id":"CVE-2022-30622"},"products":["Chcnav - P5E GNSS"],"published":"2022-07-18","related":[{"cvss_score":6.8,"headline":"Chcnav - P5E GNSS Authentication bypass admin password reset","id":"CVE-2022-30624","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":6.3,"headline":"Chcnav - P5E GNSS API not secure","id":"CVE-2022-30626","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":5.7,"headline":"Chcnav - P5E GNSS Directory listing","id":"CVE-2022-30625","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":5.7,"headline":"Chcnav - P5E GNSS Information disclosure hard coded credentials.","id":"CVE-2022-30627","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":5.3,"headline":"Chcnav - P5E GNSS Information disclosure","id":"CVE-2022-30622","kev_date_added":null,"published":"2022-07-17"}],"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-09-17","vendors":["Chcnav"]},"summary":"Attackers can bypass authentication on Chcnav P5E GNSS devices by manipulating a specific cookie value, gaining unauthorized access to the system.","url":"https://insights.sbomify.com/CVE-2022-30623/"}