{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-30354 exists.","fix":"No fix has been published for CVE-2022-30354 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30354 is a high-severity vulnerability in n/a, published on 25 Oct 2024. 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-30354 and fix it if it is affected.\n\nWhat it is: CVE-2022-30354 is a high-severity vulnerability in n/a, published on 25 Oct 2024. 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-30354 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-30354/ (Markdown: https://insights.sbomify.com/CVE-2022-30354/index.md)","id":"CVE-2022-30354","markdown":"https://insights.sbomify.com/CVE-2022-30354/index.md","name":"CVE-2022-30354","record":{"aliases":["GHSA-8gjx-cjp2-58w2"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OvalEdge data governance","requires_auth":"none","summary":"Authenticated attackers can retrieve all registered user ID numbers via a sensitive data exposure vulnerability in OvalEdge.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ovaledge","vendor":"ovaledge"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"OvalEdge 5.2.8.0 and earlier is affected by a Sensitive Data Exposure vulnerability via a GET request to /user/getUserWithTeam. Authentication is required. The information disclosed is associated with all registered user ID numbers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2022-30354","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2022-30355"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2022-30352"},"products":["n/a"],"published":"2024-10-25","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2022-30355","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":9.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-30357","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-30356","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2022-30358","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":5.4,"headline":"Information disclosure in n/a","id":"CVE-2022-30359","kev_date_added":null,"published":"2024-10-25"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2022-30360","kev_date_added":null,"published":"2024-10-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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-13","vendors":["n/a"]},"summary":"Authenticated attackers can retrieve all registered user ID numbers via a sensitive data exposure vulnerability in OvalEdge.","url":"https://insights.sbomify.com/CVE-2022-30354/"}