How severe is GHSA-mf4f-j588-5xm8?

No CVSS score has been assigned to GHSA-mf4f-j588-5xm8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mf4f-j588-5xm8?

GHSA-mf4f-j588-5xm8 affects the following packages: org.opencastproject:opencast-common (Maven), org.opencastproject:opencast-common (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mf4f-j588-5xm8?

Update org.opencastproject:opencast-common to 9.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mf4f-j588-5xm8 is resolved across your whole dependency graph.

How do I detect GHSA-mf4f-j588-5xm8 in my Maven dependencies?

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

How do I mitigate GHSA-mf4f-j588-5xm8 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-mf4f-j588-5xm8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mf4f-j588-5xm8 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-mf4f-j588-5xm8 published, and has it been updated?

GHSA-mf4f-j588-5xm8 was published on December 14, 2021 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

Apache Log4j Remote Code ExecutionGHSA-mf4f-j588-5xm8

Fix: opencast/opencast#3253

GHSA-mf4f-j588-5xm8 is a remote code execution vulnerability in org.opencastproject:opencast-common. A fix is available for org.opencastproject:opencast-common — see the affected versions and patch details below.

Published

Dec 14, 2021

Updated

Dec 2, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Real-World Exposure

2 pkgs affected

☕org.opencastproject:opencast-common☕org.opencastproject:opencast-common

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

Opencast uses an Apache Log4j2 version which, combined with older JDK versions, can be used for remote code execution attacks which have been found to be actively exploited.

Apache Log4j2 <=2.14.1 JNDI features is not sufficiently protected. An attacker who can control log messages or log message parameters can execute arbitrary code when message lookup substitution is enabled.

Who is affected

Opencast before 9.10 or 10.6 are affected
- Log4j version: all 2.x versions before 2.15.0 are affected

Patches

The issue has been fixed in Opencast 9.10 and 10.6.

Workarounds

The vulnerability can be mitigated by setting system property log4j2.formatMsgNoLookups to true.

References

For more information

If you have any questions or comments about this advisory:

Open an issue in our issue tracker
Email us at [email protected]

Note about dependencies

This issue affects many Java applications. Please also verify these are not vulnerable.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencastproject:opencast-common`	all versions	9.10`org.opencastproject:opencast-common:9.10`
☕Maven	`org.opencastproject:opencast-common`	≥ 10.0&&< 10.6	10.6`org.opencastproject:opencast-common:10.6`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:opencast-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencastproject:opencast-common to 9.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mf4f-j588-5xm8 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 Opencast uses an Apache Log4j2 version which, combined with older JDK versions, can be used for remote code execution attacks which have been found to be actively exploited. Apache Log4j2 <=2.14.1 JNDI features is not sufficiently protected. An attacker who can control log messages or log message parameters can execute arbitrary code when message lookup substitution is enabled. ### Who is affected - Opencast before 9.10 or 10.6 are affected - Log4j version: all 2.x versions before 2.15.0 are affected ### Patches The issue has been fixed in Opencast 9.10 and 10.6. ### Work

O3 Security · Impact-Aware SCA

Is GHSA-mf4f-j588-5xm8 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works