dbcve.org
Wildfly ElytronApplication · Redhat

CVE-2022-3143

HIGH · 7.4 CVSS v3.1 Published 2023-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Wildfly-elytron uses java.util.Arrays.equals for comparing sensitive values (passwords, tokens, hashes) in multiple locations. This method is vulnerable to timing attacks, allowing attackers to deduce comparing values byte-by-byte by measuring execution time differences. The fix requires using java.security.MessageDigest.isEqual which uses constant-time comparison.

MitigationReplace all instances of java.util.Arrays.equals with java.security.MessageDigest.isEqual when comparing sensitive data such as passwords, authentication tokens, or cryptographic hashes. This ensures comparison timing remains constant regardless of where mismatches occur.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wildfly ElytronApplication
Affected:= 1.15.15
Jboss Enterprise Application PlatformApplication
Affected:= 7.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Wildfly Elytron version
    Locate the wildfly-elytron jar file in the application lib or module directory, and check its version metadata (MANIFEST.MF or filename). For JBoss EAP, check the jboss-modules.jar or elytron subsystem version via CLI: /subsystem=elytron:read-resource
    Affected if The installed version is 1.15.15 for Wildfly Elytron or 7.0.0 for JBoss EAP
  2. Locate sensitive data comparison code
    Search the application codebase or decompiled elytron classes for usage of java.util.Arrays.equals being called on objects that may contain passwords, tokens, or hashes. Look for imports of java.util.Arrays and method calls to equals() in authentication-related classes.
    Affected if Code uses Arrays.equals() to compare password, token, or hash values in authentication or credential handling logic
  3. Verify constant-time comparison is not used
    Search for usage of java.security.MessageDigest.isEqual in the same codebase or elytron libraries. This is the secure replacement for constant-time comparison.
    Affected if MessageDigest.isEqual is not used for sensitive value comparisons, indicating the vulnerable Arrays.equals pattern remains in place

A system is affected if it runs Wildfly Elytron 1.15.15 or JBoss EAP 7.0.0 and uses Arrays.equals to compare passwords, tokens, or hashes without the constant-time comparison alternative.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace all instances of java.util.Arrays.equals with java.security.MessageDigest.isEqual when comparing sensitive data such as passwords, authentication tokens, or cryptographic hashes. This ensures comparison timing remains constant regardless of where mismatches occur.

Recommended fix High confidence

Wildfly Elytron 1.15.16+ or JBoss EAP 7.0.1+ (or subsequent update containing the security fix)

  1. Upgrade Wildfly Elytron to version 1.15.16 or later, which contains the fix for the timing attack vulnerability
  2. If using JBoss Enterprise Application Platform, apply the corresponding CVE-2022-3143 security patch or upgrade to a JBoss EAP version that includes the fixed Wildfly Elytron library
  3. After upgrading, verify that the application uses java.security.MessageDigest.isEqual for secure comparisons instead of java.util.Arrays.equals in any custom code that handles sensitive data such as passwords, tokens, or cryptographic keys
Caveat Minor point release upgrade; no breaking API changes expected as this is a security fix replacing an insecure method with a secure alternative

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wildfly Elytron Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3143 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3143 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data