{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-32312 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-32312 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-32312 is a low-severity authentication bypass vulnerability in UmbracoIdentityExtensions, published on 9 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-32312 and fix it if it is affected.\n\nWhat it is: CVE-2023-32312 is a low-severity authentication bypass vulnerability in UmbracoIdentityExtensions, published on 9 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-32312 in the wild and no public exploit code.\n\nAffected product: UmbracoIdentityExtensions. 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-2023-32312/ (Markdown: https://insights.sbomify.com/CVE-2023-32312/index.md)","id":"CVE-2023-32312","markdown":"https://insights.sbomify.com/CVE-2023-32312/index.md","name":"CVE-2023-32312","record":{"aliases":["GHSA-f2rf-8mwf-6jfh"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Umbraco Identity Extension","requires_auth":"none","summary":"Attackers can access protected endpoints without authentication because client secrets are not enforced in the UmbracoIdentityExtensions package.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"umbraco_identity_extensibility","vendor":"umbraco"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"UmbracoIdentityExtensions is an Umbraco add-on package that enables easy extensibility points for ASP.Net Identity integration. In affected versions client secrets are not required which may expose some endpoints to untrusted actors. Since Umbraco is not a single-page application, the implicit flow is not safe. For traditional MVC applications, it is recommended to use the authorization code flow, which requires the client to authenticate with the authorization server using a client secret. This flow provides better security, as it involves exchanging an authorization code for an access token and/or ID token, rather than directly returning tokens in the URL fragment. This issue has been patched in commit `e792429f9` and a release to Nuget is pending. Users are advised to upgrade when possible.","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":"Client secret not mandatory in UmbracoIdentityExtensions","id":"CVE-2023-32312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Inspect method manipulation in vm2","id":"CVE-2023-32313"},"packages":[],"prev":{"headline":"The CloudExplorer Lite missing permissions check","id":"CVE-2023-32311"},"products":["UmbracoIdentityExtensions"],"published":"2023-06-09","related":[],"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":"partial"},"state":"PUBLISHED","updated":"2025-01-06","vendors":["umbraco"]},"summary":"Attackers can access protected endpoints without authentication because client secrets are not enforced in the UmbracoIdentityExtensions package.","url":"https://insights.sbomify.com/CVE-2023-32312/"}