How severe is GHSA-mhgm-52vg-pvvc?

No CVSS score has been assigned to GHSA-mhgm-52vg-pvvc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mhgm-52vg-pvvc?

GHSA-mhgm-52vg-pvvc affects the following packages: com.schibsted.security:strongbox-sdk (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mhgm-52vg-pvvc?

Update com.schibsted.security:strongbox-sdk to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mhgm-52vg-pvvc is resolved across your whole dependency graph.

How do I detect GHSA-mhgm-52vg-pvvc in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.schibsted.security:strongbox-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mhgm-52vg-pvvc if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-mhgm-52vg-pvvc actively exploited in the wild?

No public exploit code has been indexed for GHSA-mhgm-52vg-pvvc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-mhgm-52vg-pvvc published, and has it been updated?

GHSA-mhgm-52vg-pvvc was published on February 16, 2023 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Privilege escalation in StrongboxGHSA-mhgm-52vg-pvvc

Fix: schibsted/strongbox@e61f7c3

GHSA-mhgm-52vg-pvvc is a security vulnerability in com.schibsted.security:strongbox-sdk. A fix is available for com.schibsted.security:strongbox-sdk — see the affected versions and patch details below.

Published

Feb 16, 2023

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.schibsted.security:strongbox-sdk

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An 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.

By 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.

Strongbox 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.

In 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.

Patches

Fixed in version 0.5.0.

Workarounds

None

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.schibsted.security:strongbox-sdk`	all versions	0.5.0`com.schibsted.security:strongbox-sdk:0.5.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.schibsted.security:strongbox-sdk, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.schibsted.security:strongbox-sdk to 0.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mhgm-52vg-pvvc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact An 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. By 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. Strongbox supports storing data in files as an alternative to DynamoDB. If the attacker had write access to where the files are stored they c

O3 Security · Impact-Aware SCA

Is GHSA-mhgm-52vg-pvvc in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works