{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41948 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41948 is a medium-severity vulnerability in dhis2-core, published on 8 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41948 and fix it if it is affected.\n\nWhat it is: CVE-2022-41948 is a medium-severity vulnerability in dhis2-core, published on 8 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-41948 in the wild and no public exploit code.\n\nAffected product: dhis2-core. 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-41948/ (Markdown: https://insights.sbomify.com/CVE-2022-41948/index.md)","id":"CVE-2022-41948","markdown":"https://insights.sbomify.com/CVE-2022-41948/index.md","name":"CVE-2022-41948","record":{"aliases":["GHSA-59fm-8432-2426"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"DHIS2 health information system","requires_auth":"high_privilege","summary":"Authenticated users with user management authority can escalate to superuser privileges via crafted HTTP requests, requiring an upgrade to secure the system.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dhis_2","vendor":"dhis2"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"DHIS 2 is an open source information system for data capture, management, validation, analytics and visualization. Affected versions are subject to a privilege escalation vulnerability. A DHIS2 user with authority to manage users can assign superuser privileges to themself by manually crafting an HTTP PUT request. Only users with the following DHIS2 user role authorities can exploit this vulnerability. Note that in many systems the only users with user admin privileges are also superusers. In these cases, the escalation vulnerability does not exist. The vulnerability is only exploitable by attackers who can authenticate as users with the user admin authority.  As this is usually a small and relatively trusted set of users, exploit vectors will often be limited. DHIS2 administrators should upgrade to the following hotfix releases: 2.36.12.1, 2.37.8.1, 2.38.2.1, 2.39.0.1. The only known workaround to this issue is to avoid the assignment of the user management authority to any users until the patch has been applied.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Privilege Chaining with the user admin role in dhis2-core","id":"CVE-2022-41948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Semi-blind Server-Side Request Forgery in dhis2-core","id":"CVE-2022-41949"},"packages":[],"prev":{"headline":"Cross-site Scripting with user-uploaded files in dhis2-core","id":"CVE-2022-41947"},"products":["dhis2-core"],"published":"2022-12-08","related":[{"cvss_score":8.8,"headline":"SQL Injection in DHIS2's in OrgUnit program association","id":"CVE-2022-24848","kev_date_added":null,"published":"2022-06-01"},{"cvss_score":8.8,"headline":"SQL Injection in DHIS2 Tracker API","id":"CVE-2021-39179","kev_date_added":null,"published":"2021-10-29"},{"cvss_score":8.5,"headline":"Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in dhis2-core","id":"CVE-2021-32704","kev_date_added":null,"published":"2021-06-24"},{"cvss_score":8.1,"headline":"SQL Injection in DHIS2 Tracker API","id":"CVE-2021-41187","kev_date_added":null,"published":"2021-11-01"},{"cvss_score":7.1,"headline":"DHIS2 Core vulnerable to Improper Access Control with PATCH requests","id":"CVE-2023-31138","kev_date_added":null,"published":"2023-05-09"},{"cvss_score":6.5,"headline":"Missing authorization in dhis2-core","id":"CVE-2023-32060","kev_date_added":null,"published":"2023-05-09"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["dhis2"]},"summary":"Authenticated users with user management authority can escalate to superuser privileges via crafted HTTP requests, requiring an upgrade to secure the system.","url":"https://insights.sbomify.com/CVE-2022-41948/"}