Skip to content
Noroxi
CVE-2023-0105· NVD / CVE Program· CNA redhat

A flaw was found in Keycloak.

Noroxi assessment

Priority: Monitor (action score 26/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.4% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: org.keycloak:keycloak-core (Maven) 22.0.1; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7.6::el7) 0:18.0.11-2.redhat_00001.1.el7sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7.6::el7) 0:18.0.11-2.redhat_00001.1.el7sso.

Low priority for now. Upgrade to org.keycloak:keycloak-core (Maven) 22.0.1; rh-sso7-keycloak (Red Hat:red_hat_single_sign_on:7.6::el7) 0:18.0.11-2.redhat_00001.1.el7sso; rh-sso7-keycloak-server (Red Hat:red_hat_single_sign_on:7.6::el7) 0:18.0.11-2.redhat_00001.1.el7sso or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A flaw was found in Keycloak. This flaw allows impersonation and lockout due to the email trust not being handled correctly in Keycloak. An attacker can shadow other users with the same email and lockout or impersonate them.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Jan 13, 2023
Updated
Jun 17, 2026
EPSS
0.7% · 53th percentile

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-0105

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
redhatkeycloak
redhatsingle sign-on

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redhat keycloakall versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • redhat.com Keycloak

    • n/aunknown

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.keycloak:keycloak-corebefore 22.0.122.0.1
Red Hat:red_hat_single_sign_on:7.6::el7rh-sso7-keycloakbefore 0:18.0.11-2.redhat_00001.1.el7sso0:18.0.11-2.redhat_00001.1.el7sso
Red Hat:red_hat_single_sign_on:7.6::el7rh-sso7-keycloak-serverbefore 0:18.0.11-2.redhat_00001.1.el7sso0:18.0.11-2.redhat_00001.1.el7sso
Red Hat:red_hat_single_sign_on:7.6::el8rh-sso7-keycloakbefore 0:18.0.11-2.redhat_00001.1.el8sso0:18.0.11-2.redhat_00001.1.el8sso
Red Hat:red_hat_single_sign_on:7.6::el8rh-sso7-keycloak-serverbefore 0:18.0.11-2.redhat_00001.1.el8sso0:18.0.11-2.redhat_00001.1.el8sso
Red Hat:red_hat_single_sign_on:7.6::el9rh-sso7-keycloakbefore 0:18.0.11-2.redhat_00001.1.el9sso0:18.0.11-2.redhat_00001.1.el9sso
Red Hat:red_hat_single_sign_on:7.6::el9rh-sso7-keycloak-serverbefore 0:18.0.11-2.redhat_00001.1.el9sso0:18.0.11-2.redhat_00001.1.el9sso

Other highest-scoring records for the same primary product.

  • CVE-2020-10770A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter
    42Plan
  • CVE-2022-1245A privilege escalation flaw was found in the token exchange feature of keycloak.
    39Monitor
  • CVE-2019-14910A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS fro
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-3782Jan 13, 2023 · keycloak: path traversal via double URL encoding.
    38Monitor
  • ← EarlierCVE-2023-0091Jan 13, 2023 · A flaw was found in Keycloak, where it did not properly check client tokens for possible revocation in its client credential flow.
    15Monitor
  • Later →CVE-2022-1274Mar 29, 2023 · A flaw was found in Keycloak in the execute-actions-email endpoint.
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.keycloak:keycloak-core22.0.1Package registry (OSV)
red hat:rh-sso7-keycloak0:18.0.11-2.redhat_00001.1.el7sso · Red Hat:red_hat_single_sign_on:7.6::el7Package registry (OSV)
red hat:rh-sso7-keycloak-server0:18.0.11-2.redhat_00001.1.el7sso · Red Hat:red_hat_single_sign_on:7.6::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
Low

CVSS vector

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

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records