{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22798 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22798 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22798 is a medium-severity missing authorization vulnerability in Sysaid, published on 12 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-22798 and fix it if it is affected.\n\nWhat it is: CVE-2022-22798 is a medium-severity missing authorization vulnerability in Sysaid, published on 12 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-22798 in the wild and no public exploit code.\n\nAffected product: Sysaid. 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-22798/ (Markdown: https://insights.sbomify.com/CVE-2022-22798/index.md)","id":"CVE-2022-22798","markdown":"https://insights.sbomify.com/CVE-2022-22798/index.md","name":"CVE-2022-22798","record":{"aliases":["GHSA-6xc5-p2xh-3cfm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SysAid Help Desk","requires_auth":"low_privilege","summary":"An attacker can bypass authentication to access the dashboard, read sensitive data, and modify records by manipulating the URL path.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCD","cpe":[{"product":"sysaid","vendor":"sysaid"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[],"description":"Sysaid – Pro Plus Edition, SysAid Help Desk Broken Access Control v20.4.74 b10, v22.1.20 b62, v22.1.30 b49 - An attacker needs to log in as a guest after that the system redirects him to the service portal or EndUserPortal.JSP, then he needs to change the path in the URL to /ConcurrentLogin%2ejsp after that he will receive an error message with a login button, by clicking on it, he will connect to the system dashboard. The attacker can receive sensitive data like server details, usernames, workstations, etc. He can also perform actions such as uploading files, deleting calls from the system.","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":"Sysaid – Pro Plus Edition, SysAid Help Desk Broken Access Control","id":"CVE-2022-22798","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in EcoStruxure Power Monitoring Expert (Versions 2020 and prior)","id":"CVE-2022-22804"},"packages":[],"prev":{"headline":"Sysaid – sysaid Open Redirect","id":"CVE-2022-22797"},"products":["Sysaid"],"published":"2022-05-12","related":[{"cvss_score":9.8,"headline":"SysAid Server Path Traversal","id":"CVE-2023-47246","kev_date_added":"2023-11-13","published":"2023-11-10"},{"cvss_score":9.3,"headline":"SysAid On-Prem Improper Restriction of XML External Entity Reference","id":"CVE-2025-2775","kev_date_added":"2025-07-22","published":"2025-05-07"},{"cvss_score":9.3,"headline":"SysAid On-Prem Improper Restriction of XML External Entity Reference","id":"CVE-2025-2776","kev_date_added":"2025-07-22","published":"2025-05-07"},{"cvss_score":9.9,"headline":"SysAid - CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')","id":"CVE-2024-36393","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.3,"headline":"SysAid On-Prem \u003c= 23.3.40 lshw Proceessing XML External Entity Injection","id":"CVE-2025-2777","kev_date_added":null,"published":"2025-05-07"},{"cvss_score":9.1,"headline":"SysAid - CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')","id":"CVE-2024-36394","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2021-43971","kev_date_added":null,"published":"2022-01-11"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["SysAid"]},"summary":"An attacker can bypass authentication to access the dashboard, read sensitive data, and modify records by manipulating the URL path.","url":"https://insights.sbomify.com/CVE-2022-22798/"}