{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-59044 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-59044 is a medium-severity vulnerability in himmelblau-idm himmelblau, published on 9 Sep 2025. 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-2025-59044 and fix it if it is affected.\n\nWhat it is: CVE-2025-59044 is a medium-severity vulnerability in himmelblau-idm himmelblau, published on 9 Sep 2025. 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-2025-59044 in the wild and no public exploit code.\n\nAffected product: himmelblau-idm himmelblau. 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-2025-59044/ (Markdown: https://insights.sbomify.com/CVE-2025-59044/index.md)","id":"CVE-2025-59044","markdown":"https://insights.sbomify.com/CVE-2025-59044/index.md","name":"CVE-2025-59044","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Azure Entra ID integration","requires_auth":"low_privilege","summary":"Attackers can gain unauthorized access to resources by creating Entra ID groups with names matching privileged groups, causing GID collisions on Himmelblau-joined Linux hosts.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"Himmelblau is an interoperability suite for Microsoft Azure Entra ID and Intune. Himmelblau 0.9.x derives numeric GIDs for Entra ID groups from the group display name when himmelblau.conf `id_attr_map = name` (the default configuration). Because Microsoft Entra ID allows multiple groups with the same `displayName` (including end-user–created personal/O365 groups, depending on tenant policy), distinct directory groups can collapse to the same numeric GID on Linux. This issue only applies to Himmelblau versions 0.9.0 through 0.9.22. Any resource or service on a Himmelblau-joined host that enforces authorization by numeric GID (files/dirs, etc.) can be unintentionally accessible to a user who creates or joins a different Entra/O365 group that happens to share the same `displayName` as a privileged security group. Users should upgrade to 0.9.23, or 1.0.0 or later, to receive a patch. Group to GID mapping now uses Entra ID object IDs (GUIDs) and does not collide on same-name groups. As a workaround, use tenant policy hardening to restrict arbitrary group creation until all hosts are patched.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Himmelblau vulnerable to GID collision via group name-derived mapping (privilege escalation)","id":"CVE-2025-59044","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Stalwart vulnerable to Memory Exhaustion via CalDAV Event Expansion","id":"CVE-2025-59045"},"packages":[],"prev":{"headline":"OpenBao vulnerable to denial of service via malicious JSON request processing","id":"CVE-2025-59043"},"products":["himmelblau"],"published":"2025-09-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-09-10","vendors":["himmelblau-idm"]},"summary":"Attackers can gain unauthorized access to resources by creating Entra ID groups with names matching privileged groups, causing GID collisions on Himmelblau-joined Linux hosts.","url":"https://insights.sbomify.com/CVE-2025-59044/"}