{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-20903 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-20903 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-20903 is a medium-severity authentication bypass vulnerability in Cloud Foundry, published on 28 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-20903 and fix it if it is affected.\n\nWhat it is: CVE-2023-20903 is a medium-severity authentication bypass vulnerability in Cloud Foundry, published on 28 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-20903 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry. 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-20903/ (Markdown: https://insights.sbomify.com/CVE-2023-20903/index.md)","id":"CVE-2023-20903","markdown":"https://insights.sbomify.com/CVE-2023-20903/index.md","name":"CVE-2023-20903","record":{"aliases":["GHSA-5rqc-wqwj-478f"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloud Foundry UAA","requires_auth":"low_privilege","summary":"Attackers with valid refresh tokens from a deactivated identity provider can bypass authentication and access Cloud Foundry resources.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"user_account_and_authentication","vendor":"cloudfoundry"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"This disclosure regards a vulnerability related to UAA refresh tokens and external identity providers.Assuming that an external identity provider is linked to the UAA, a refresh token is issued to a client on behalf of a user from that identity provider, the administrator of the UAA deactivates the identity provider from the UAA. It is expected that the UAA would reject a refresh token during a refresh token grant, but it does not (hence the vulnerability). It will continue to issue access tokens to request presenting such refresh tokens, as if the identity provider was still active. As a result, clients with refresh tokens issued through the deactivated identity provider would still have access to Cloud Foundry resources until their refresh token expires (which defaults to 30 days).","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":"Auth bypass in Cloud Foundry","id":"CVE-2023-20903","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in Android","id":"CVE-2023-20904"},"packages":[],"prev":{"headline":"Timing attack risk in Harbor","id":"CVE-2023-20902"},"products":["Cloud Foundry"],"published":"2023-03-28","related":[{"cvss_score":8.7,"headline":"Privilege Escalation via Blind SCIM Injection in UAA","id":"CVE-2019-11278","kev_date_added":null,"published":"2019-09-26"},{"cvss_score":4.3,"headline":"UAA SCIM Filter XSS","id":"CVE-2019-11274","kev_date_added":null,"published":"2019-08-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":"partial"},"state":"PUBLISHED","updated":"2025-02-19","vendors":["n/a"]},"summary":"Attackers with valid refresh tokens from a deactivated identity provider can bypass authentication and access Cloud Foundry resources.","url":"https://insights.sbomify.com/CVE-2023-20903/"}