{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2017:2628-1 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2017:2628-1 is a missing authorization vulnerability in openstack-glance, published on 2 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for SUSE-SU-2017:2628-1 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2017:2628-1 is a missing authorization vulnerability in openstack-glance, published on 2 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of SUSE-SU-2017:2628-1 in the wild and no public exploit code.\n\nAffected product: openstack-glance. 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/SUSE-SU-2017-2628-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2017-2628-1/index.md)","id":"SUSE-SU-2017:2628-1","markdown":"https://insights.sbomify.com/SUSE-SU-2017-2628-1/index.md","name":"SUSE-SU-2017:2628-1","record":{"aliases":[],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenStack Glance","requires_auth":"low_privilege","summary":"An authenticated user can modify image location metadata if multiple locations are enabled, leading to unauthorized data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for openstack-glance fixes the following issues:\n\n- Restrict image_location metadata \n  When `show_multiple_locations` is enabled in Glance, any user can\n  rewrite the metadata information for locations, causing a security\n  breach. (bsc#1023507)","ecosystems":["SUSE:OpenStack Cloud 7"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for openstack-glance","id":"SUSE-SU-2017:2628-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2017"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"SUSE:OpenStack Cloud 7","fixed":["13.0.1~a0~dev6-4.3.1"],"introduced":["0"],"last_affected":[],"package":"openstack-glance","purl":"pkg:rpm/suse/openstack-glance\u0026distro=SUSE%20OpenStack%20Cloud%207","source":"SUSE-SU-2017:2628-1"},{"ecosystem":"SUSE:OpenStack Cloud 7","fixed":["13.0.1~a0~dev6-4.3.4"],"introduced":["0"],"last_affected":[],"package":"openstack-glance-doc","purl":"pkg:rpm/suse/openstack-glance-doc\u0026distro=SUSE%20OpenStack%20Cloud%207","source":"SUSE-SU-2017:2628-1"}],"products":null,"published":"2017-10-02","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An authenticated user can modify image location metadata if multiple locations are enabled, leading to unauthorized data modification.","url":"https://insights.sbomify.com/SUSE-SU-2017-2628-1/"}