{"answers":{"affected":"2 open source packages ship an affected version, including com.schibsted.security:strongbox-sdk.","exploited":"There is no known exploitation of GHSA-mhgm-52vg-pvvc in the wild and no public exploit code.","fix":"Upgrade com.schibsted.security:strongbox-sdk to 0.5.0 or later.","what":"GHSA-mhgm-52vg-pvvc is a vulnerability in com.schibsted.security:strongbox-sdk, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-mhgm-52vg-pvvc and fix it if it is affected.\n\nWhat it is: GHSA-mhgm-52vg-pvvc is a vulnerability in com.schibsted.security:strongbox-sdk, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-mhgm-52vg-pvvc in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.schibsted.security:strongbox-sdk (Maven): affected all versions; fixed in 0.5.0\n- com.schibsted.security:strongbox-sdk (Maven): affected all versions; fixed in 0.5.0\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/GHSA-mhgm-52vg-pvvc/ (Markdown: https://insights.sbomify.com/GHSA-mhgm-52vg-pvvc/index.md)","id":"GHSA-mhgm-52vg-pvvc","markdown":"https://insights.sbomify.com/GHSA-mhgm-52vg-pvvc/index.md","name":"GHSA-mhgm-52vg-pvvc","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Java encryption library","requires_auth":"low_privilege","summary":"An attacker with read-only access can craft valid encrypted secrets to escalate privileges or modify data if write access to storage is also available.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\nAn attacker with read-only access to a Strongbox secret could craft a valid encrypted secret (same id/version). It also makes the audit logs from KMS less useful. The issue is caused by a bug in the underlying AWS Encryption SDK.\n\nBy default, the encrypted secrets are stored in DynamoDB and an attacker with read-only access would not be able to write the encrypted secret to DynamoDB. So in practice the impact should be limited for most users.\n\nStrongbox supports storing data in files as an alternative to DynamoDB. If the attacker had write access to where the files are stored they could make the attack work end-to-end. Similarly, any custom storage backend could also be affected.\n\nIn order to be backwards compatible Strongbox will not make use of key commitments (another improvement to the AWS Encryption SDK). Strongbox enforces that only one KMS key can be used, and it must match the expected one. This means that an attacker needs write access to both KMS and DynamoDB (or other storage backend) to stage an attack, which is not a scenario Strongbox is designed to protect against.\n\n### Patches\nFixed in version 0.5.0.\n\n### Workarounds\nNone\n\n### References\n- https://github.com/aws/aws-encryption-sdk-java/security/advisories/GHSA-55xh-53m6-936r\n- https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/concepts.html#key-commitment","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Privilege escalation in Strongbox","id":"GHSA-mhgm-52vg-pvvc","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"com.schibsted.security:strongbox-sdk","purl":null,"source":"GHSA-mhgm-52vg-pvvc"},{"ecosystem":"Maven","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"com.schibsted.security:strongbox-sdk","purl":"pkg:maven/com.schibsted.security/strongbox-sdk","source":"GHSA-mhgm-52vg-pvvc"}],"products":null,"published":"2023-02-16","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker with read-only access can craft valid encrypted secrets to escalate privileges or modify data if write access to storage is also available.","url":"https://insights.sbomify.com/GHSA-mhgm-52vg-pvvc/"}