Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕ Maven

GHSA-jmj6-p2j9-68cp

HIGH

GHSA-jmj6-p2j9-68cp is a high-severity (CVSS 7.4) CWE-203 vulnerability in org.wildfly.security:wildfly-elytron. O3 Security confirms whether GHSA-jmj6-p2j9-68cp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Wildfly-elytron possibly vulnerable to timing attacks via use of unsafe comparator

Also known asCVE-2022-3143
Published
Jan 13, 2023
Updated
Nov 8, 2023
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Real-World Exposure

2 pkgs affected
☕org.wildfly.security:wildfly-elytron☕org.wildfly.security:wildfly-elytron

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

wildfly-elytron: possible timing attacks via use of unsafe comparator. A flaw was found in Wildfly-elytron. Wildfly-elytron uses java.util.Arrays.equals in several places, which is unsafe and vulnerable to timing attacks. To compare values securely, use java.security.MessageDigest.isEqual instead. This flaw allows an attacker to access secure information or impersonate an authed user.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.wildfly.security:wildfly-elytronall versions1.15.15.Final
☕Mavenorg.wildfly.security:wildfly-elytron≥ 1.16.0.CR1&&< 1.20.3.Final1.20.3.Final

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wildfly.security:wildfly-elytron. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.wildfly.security:wildfly-elytron to 1.15.15.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jmj6-p2j9-68cp is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-jmj6-p2j9-68cp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jmj6-p2j9-68cp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

wildfly-elytron: possible timing attacks via use of unsafe comparator. A flaw was found in Wildfly-elytron. Wildfly-elytron uses `java.util.Arrays.equals` in several places, which is unsafe and vulnerable to timing attacks. To compare values securely, use `java.security.MessageDigest.isEqual` instead. This flaw allows an attacker to access secure information or impersonate an authed user.
O3 Security · Impact-Aware SCA

Is GHSA-jmj6-p2j9-68cp in your dependencies?

O3 detects GHSA-jmj6-p2j9-68cp across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works