{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-49012 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-49012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-49012 is a medium-severity authentication bypass vulnerability in himmelblau-idm himmelblau, published on 5 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-49012 and fix it if it is affected.\n\nWhat it is: CVE-2025-49012 is a medium-severity authentication bypass vulnerability in himmelblau-idm himmelblau, published on 5 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-49012 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-49012/ (Markdown: https://insights.sbomify.com/CVE-2025-49012/index.md)","id":"CVE-2025-49012","markdown":"https://insights.sbomify.com/CVE-2025-49012/index.md","name":"CVE-2025-49012","record":{"aliases":["GHSA-gcxr-m95v-qcf7"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Azure Entra ID integration","requires_auth":"low_privilege","summary":"Attackers can bypass login restrictions by creating Entra ID groups with duplicate display names, gaining unauthorized access or sudo privileges.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Himmelblau is an interoperability suite for Microsoft Azure Entra ID and Intune. Himmelblau versions 0.9.0 through 0.9.14 and 1.00-alpha are vulnerable to a privilege escalation issue when Entra ID group-based access restrictions are configured using group display names instead of object IDs. Starting in version 0.9.0, Himmelblau introduced support for specifying group names in the `pam_allow_groups` configuration option. However, Microsoft Entra ID permits the creation of multiple groups with the same `displayName` via the Microsoft Graph API—even by non-admin users, depending on tenant settings. As a result, a user could create a personal group with the same name as a legitimate access group (e.g., `\"Allow-Linux-Login\"`), add themselves to it, and be granted authentication or `sudo` rights by Himmelblau. Because affected Himmelblau versions compare group names by either `displayName` or by the immutable `objectId`, this allows bypassing access control mechanisms intended to restrict login to members of official, centrally-managed groups. This issue is fixed in Himmelblau version **0.9.15** and later. In these versions, group name matching in `pam_allow_groups` has been deprecated and removed, and only group `objectId`s (GUIDs) may be specified for secure group-based filtering. To mitigate the issue without upgrading, replace all entries in `pam_allow_groups` with the objectId of the target Entra ID group(s) and/or audit your tenant for groups with duplicate display names using the Microsoft Graph API.","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":"Himmelblau's Name-Based Group Matching in `pam_allow_groups` Leads to Potential Security Bypass","id":"CVE-2025-49012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"WilderForge vulnerable to code Injection via GitHub Actions Workflows","id":"CVE-2025-49013"},"packages":[],"prev":{"headline":"SpiceDB checks involving relations with caveats can result in no permission when permission is expected","id":"CVE-2025-49011"},"products":["himmelblau"],"published":"2025-06-05","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-06-09","vendors":["himmelblau-idm"]},"summary":"Attackers can bypass login restrictions by creating Entra ID groups with duplicate display names, gaining unauthorized access or sudo privileges.","url":"https://insights.sbomify.com/CVE-2025-49012/"}