How severe is GHSA-42xw-p62x-hwcf?

GHSA-42xw-p62x-hwcf has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-42xw-p62x-hwcf?

GHSA-42xw-p62x-hwcf affects the following packages: org.apache.derby:derby (Maven). Ecosystems affected: Maven.

How do I fix GHSA-42xw-p62x-hwcf?

Update org.apache.derby:derby to 10.14.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-42xw-p62x-hwcf is resolved across your whole dependency graph.

How do I detect GHSA-42xw-p62x-hwcf in my Maven dependencies?

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

How do I mitigate GHSA-42xw-p62x-hwcf 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-42xw-p62x-hwcf actively exploited in the wild?

No public exploit code has been indexed for GHSA-42xw-p62x-hwcf 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.

What is the EPSS score for GHSA-42xw-p62x-hwcf?

GHSA-42xw-p62x-hwcf has an EPSS (Exploit Prediction Scoring System) score of 4.6%, placing it in the 92th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-42xw-p62x-hwcf published, and has it been updated?

GHSA-42xw-p62x-hwcf was published on May 13, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Improper Access Control in Apache Derby (Medium 5.3)

EPSS Exploitation Probability

via FIRST.org ↗

4.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs92th percentile — riskier than 92% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.derby:derby

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

In Apache Derby 10.3.1.4 to 10.14.1.0, a specially-crafted network packet can be used to request the Derby Network Server to boot a database whose location and contents are under the user's control. If the Derby Network Server is not running with a Java Security Manager policy file, the attack is successful. If the server is using a policy file, the policy file must permit the database location to be read for the attack to work. The default Derby Network Server policy file distributed with the affected releases includes a permissive policy as the default Network Server policy, which allows the attack to work.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.derby:derby`	≥ 10.3.1.4&&< 10.14.2.0	10.14.2.0`org.apache.derby:derby:10.14.2.0`

Affected Products

2 products · 2 configurations

Application

derbyapache

≥ 10.3.1.4 && ≤ 10.14.1.0

range

Application

weblogic serveroracle

1 version

12.2.1.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.derby:derby, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.derby:derby to 10.14.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-42xw-p62x-hwcf 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

In Apache Derby 10.3.1.4 to 10.14.1.0, a specially-crafted network packet can be used to request the Derby Network Server to boot a database whose location and contents are under the user's control. If the Derby Network Server is not running with a Java Security Manager policy file, the attack is successful. If the server is using a policy file, the policy file must permit the database location to be read for the attack to work. The default Derby Network Server policy file distributed with the affected releases includes a permissive policy as the default Network Server policy, which allows the

O3 Security · Impact-Aware SCA

Is GHSA-42xw-p62x-hwcf in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Improper Access Control in Apache DerbyGHSA-42xw-p62x-hwcf

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored