Skip to content
Fencer Intel
medium 6.6

CVE-2019-10170 json

Privilege Defined With Unsafe Actions in Keycloak

published 2020-05-08 6 y ago modified 2026-06-17 4 mo ago also GHSA-7m27-3587-83xf , EUVD-2021-2173

cvss
6.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

A flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy. This flaw allows an attacker with authenticated user and realm management permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the application user.

Patch / fix

  • maven org.keycloak:keycloak-core 8.0.0
  • redhat keycloak 8.0.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-10170 updated cvss 6.6

keycloak: script execution via realm management policy trigger

  • Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
    affected: no fix available
  • Red Hat Single Sign-On 7.3.4 zip
    fixed: vendor fix RHSA-2019:3050

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P
GitHub 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-core
<8.0.0
8.0.0

Affected products

  • [UNKNOWN] keycloak

Classification

Weakness
  • CWE-267 Privilege Defined With Unsafe Actions

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.