Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 4 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,764exploited flaws on CISA’s list
35added in the last 30 days
457new WordPress flaws this week
390,714entries in the database

358 results · page 7 of 8

  • Dec 15, 2020A flaw was found in Keycloak before 13.0.0 where an external identity provider, after successful authentication, redirects to a Keycloak endpoint that accepts mCVE-2020-14302 · Other software · Redhat · reported by Red HatMedium 4.9

    A flaw was found in Keycloak before 13.0.0 where an external identity provider, after successful authentication, redirects to a Keycloak endpoint that accepts multiple invocations with the use of the same "state" parameter. This flaw allows a malicious user to perform replay attacks.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 15, 2020A 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 request_uri.CVE-2020-10770 · Other software · Redhat · reported by Red HatMedium 5.3

    A 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 request_uri. This flaw allows an attacker to use this parameter to execute a Server-side request forgery (SSRF) attack.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 16, 2020It was found that Keycloak before version 12.0.0 would permit a user with only view-profile role to manage the resources in the new account console, allowing acCVE-2020-14389 · Other software · Redhat · reported by Red HatHigh 8.1

    It was found that Keycloak before version 12.0.0 would permit a user with only view-profile role to manage the resources in the new account console, allowing access and modification of data the user was not intended to have.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 16, 2020A flaw was found in Keycloak before version 12.0.0, where it is possible to add unsafe schemes for the redirect_uri parameter.CVE-2020-10776 · Other software · Redhat · reported by Red HatMedium 4.8

    A flaw was found in Keycloak before version 12.0.0, where it is possible to add unsafe schemes for the redirect_uri parameter. This flaw allows an attacker to perform a Cross-site scripting attack.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 9, 2020A vulnerability was found in keycloak, where path traversal using URL-encoded path segments in the request is possible because the resources endpoint applies a CVE-2020-14366 · Other software · Red Hat · reported by Red HatMedium 6.8

    A vulnerability was found in keycloak, where path traversal using URL-encoded path segments in the request is possible because the resources endpoint applies a transformation of the url path to the file path. Only few specific folder hierarchies can be exposed by this flaw

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 16, 2020A flaw was found in all versions of Keycloak before 10.0.0, where the NodeJS adapter did not support the verify-token-audience.CVE-2020-1694 · Other software · Redhat · reported by Red HatMedium 4.9

    A flaw was found in all versions of Keycloak before 10.0.0, where the NodeJS adapter did not support the verify-token-audience. This flaw results in some users having access to sensitive information outside of their permissions.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 16, 2020A flaw was found in Keycloak's data filter, in version 10.0.1, where it allowed the processing of data URLs in some circumstances.CVE-2020-10748 · Other software · Redhat · reported by Red HatMedium 6.1

    A flaw was found in Keycloak's data filter, in version 10.0.1, where it allowed the processing of data URLs in some circumstances. This flaw allows an attacker to conduct cross-site scripting or further attacks.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Sep 16, 2020A vulnerability was found in Keycloak before 11.0.1 where DoS attack is possible by sending twenty requests simultaneously to the specified keycloak server, allCVE-2020-10758 · Other software · Redhat · reported by Red HatHigh 7.5

    A vulnerability was found in Keycloak before 11.0.1 where DoS attack is possible by sending twenty requests simultaneously to the specified keycloak server, all with a Content-Length header value that exceeds the actual byte count of the request body.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 22, 2020A vulnerability was found in Keycloak before 9.0.2, where every Authorization URL that points to an IDP server lacks proper input validation as it allows a wideCVE-2020-1727 · Other software · [UNKNOWN] · reported by Red HatMedium 6.4

    A vulnerability was found in Keycloak before 9.0.2, where every Authorization URL that points to an IDP server lacks proper input validation as it allows a wide range of characters. This flaw allows a malicious to craft deep links that introduce further attack scenarios on affected clients.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 15, 2020A flaw was found in Keycloak in versions before 10.0.0, where it does not perform the TLS hostname verification while sending emails using the SMTP server.CVE-2020-1758 · Other software · Red Hat · reported by Red HatMedium 5.3

    A flaw was found in Keycloak in versions before 10.0.0, where it does not perform the TLS hostname verification while sending emails using the SMTP server. This flaw allows an attacker to perform a man-in-the-middle (MITM) attack.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 13, 2020A flaw was found in Keycloak before version 11.0.0, where the code base contains usages of ObjectInputStream without type checks.CVE-2020-1714 · Other software · Red Hat · reported by Red HatHigh 8.8

    A flaw was found in Keycloak before version 11.0.0, where the code base contains usages of ObjectInputStream without type checks. This flaw allows an attacker to inject arbitrarily serialized Java Objects, which would then get deserialized in a privileged context and potentially lead to remote code execution.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 12, 2020A flaw was found in the reset credential flow in all Keycloak versions before 8.0.0.CVE-2020-1718 · Other software · Red Hat · reported by Red HatHigh 7.1

    A flaw was found in the reset credential flow in all Keycloak versions before 8.0.0. This flaw allows an attacker to gain unauthorized access to the application.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 11, 2020A flaw was found in Keycloak in versions before 9.0.2.CVE-2020-1724 · Other software · Red Hat · reported by Red HatMedium 4.3

    A flaw was found in Keycloak in versions before 9.0.2. This flaw allows a malicious user that is currently logged in, to see the personal information of a previously logged out user in the account manager section.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 11, 2020A flaw was found in keycloak in versions before 9.0.0.CVE-2020-1698 · Other software · Red Hat · reported by Red HatMedium 5

    A flaw was found in keycloak in versions before 9.0.0. A logged exception in the HttpMethod class may leak the password given as parameter. The highest threat from this vulnerability is to data confidentiality.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 8, 2020A flaw was found in the Keycloak admin console, where the realm management interface permits a script to be set via the policy.CVE-2019-10170 · Other software · [UNKNOWN] · reported by Red HatMedium 6.6

    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.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 8, 2020A flaw was found in Keycloak’s user-managed access interface, where it would permit a script to be set in the UMA policy.CVE-2019-10169 · Other software · [UNKNOWN] · reported by Red HatMedium 6.6

    A flaw was found in Keycloak’s user-managed access interface, where it would permit a script to be set in the UMA policy. This flaw allows an authenticated attacker with UMA permissions to configure a malicious script to trigger and execute arbitrary code with the permissions of the user running application.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • May 4, 2020A flaw was found in Keycloak version 8.0.2 and 9.0.0, and was fixed in Keycloak version 9.0.1, where a malicious user registers as oneself.CVE-2020-10686 · Other software · Keycloak · reported by Red HatMedium 4.1

    A flaw was found in Keycloak version 8.0.2 and 9.0.0, and was fixed in Keycloak version 9.0.1, where a malicious user registers as oneself. The attacker could then use the remove devices form to post different credential IDs and possibly remove MFA devices for other users.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 6, 2020A vulnerability was found in all versions of Keycloak where, the pages on the Admin Console area of the application are completely missing general HTTP securityCVE-2020-1728 · Other software · [UNKNOWN] · reported by Red HatMedium 4.8

    A vulnerability was found in all versions of Keycloak where, the pages on the Admin Console area of the application are completely missing general HTTP security headers in HTTP-responses. This does not directly lead to a security issue, yet it might aid attackers in their efforts to exploit other problems. The flaws unnecessarily make the servers more prone to Clickjacking, channel downgrade attacks and other similar client-based attack vectors.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 24, 2020A flaw was found in keycloak before version 9.0.1.CVE-2020-1744 · Other software · Red Hat · reported by Red HatMedium 5.6

    A flaw was found in keycloak before version 9.0.1. When configuring an Conditional OTP Authentication Flow as a post login flow of an IDP, the failure login events for OTP are not being sent to the brute force protection event queue. So BruteForceProtector does not handle this events.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 2, 2020A flaw was found in all versions of the Keycloak operator, before version 8.0.2,(community only) where the operator generates a random admin password when instaCVE-2020-1731 · Other software · Red Hat · reported by Red HatCritical 9.1

    A flaw was found in all versions of the Keycloak operator, before version 8.0.2,(community only) where the operator generates a random admin password when installing Keycloak, however the password remains the same when deployed to the same OpenShift namespace.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 10, 2020It was found in all keycloak versions before 9.0.0 that links to external applications (Application Links) in the admin console are not validated properly and cCVE-2020-1697 · Other software · Red Hat · reported by Red HatMedium 6.1

    It was found in all keycloak versions before 9.0.0 that links to external applications (Application Links) in the admin console are not validated properly and could allow Stored XSS attacks. An authed malicious user could create URLs to trick users in other realms, and possibly conduct further attacks.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 8, 2020It was found that keycloak before version 8.0.0 exposes internal adapter endpoints in org.keycloak.constants.AdapterConstants, which can be invoked via a speciaCVE-2019-14820 · Other software · keycloak · reported by Red HatMedium 4.3

    It was found that keycloak before version 8.0.0 exposes internal adapter endpoints in org.keycloak.constants.AdapterConstants, which can be invoked via a specially-crafted URL. This vulnerability could allow an attacker to access unauthorized information.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 7, 2020A flaw was found in keycloack before version 8.0.0.CVE-2019-14837 · Other software · Red Hat · reported by Red HatCritical 9.1

    A flaw was found in keycloack before version 8.0.0. The owner of 'placeholder.org' domain can setup mail server on this domain and knowing only name of a client can reset password and then log in. For example, for client name 'test' the email address will be 'service-account-test@placeholder.org'.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 15, 2019JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL.CVE-2014-3652 · Other software · JBoss KeyCloak · reported by Red HatMedium 6.1

    JBoss KeyCloak: Open redirect vulnerability via failure to validate the redirect URL.

    Product
    JBoss KeyCloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 10, 2019JBoss KeyCloak: XSS in login-status-iframe.htmlCVE-2014-3656 · Other software · JBoss KeyCloak · reported by Red HatMedium 6.1

    JBoss KeyCloak: XSS in login-status-iframe.html

    Product
    JBoss KeyCloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 6, 2019In SecureWorks Red Cloak Windows Agent before 2.0.7.9, a local user can bypass the generation of telemetry alerts by removing NT AUTHORITY\SYSTEM permissions frCVE-2019-19620 · Other software · Dell · reported by MITRELow 3.3

    In SecureWorks Red Cloak Windows Agent before 2.0.7.9, a local user can bypass the generation of telemetry alerts by removing NT AUTHORITY\SYSTEM permissions from a file. This is limited in scope to the collection of process-execution telemetry, for executions against specific files where the SYSTEM user was denied access to the source file.

    Product
    RED Cloak Windows Agent
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 5, 2019A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS from the LDAP server (lCVE-2019-14910 · Other software · Redhat · reported by Red HatCritical 9.8

    A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS from the LDAP server (ldaps), in this case user authentication succeeds even if invalid password has entered.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Dec 4, 2019A vulnerability was found in Keycloak 7.x where the user federation LDAP bind type is none (LDAP anonymous bind), any password, invalid or valid will be accepteCVE-2019-14909 · Other software · Redhat · reported by Red HatHigh 8.3

    A vulnerability was found in Keycloak 7.x where the user federation LDAP bind type is none (LDAP anonymous bind), any password, invalid or valid will be accepted.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 13, 2019JBoss KeyCloak is vulnerable to soft token deletion via CSRFCVE-2014-3655 · Other software · JBoss · reported by Red HatMedium 4.3

    JBoss KeyCloak is vulnerable to soft token deletion via CSRF

    Product
    KeyCloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 5, 2019CloakCoin through 2.2.2.0 (a chain-based proof-of-stake cryptocurrency) allows a remote denial of service, exploitable by an attacker who acquires even a small CVE-2018-19167 · Other software · Cloakcoin · reported by MITREHigh 7.5

    CloakCoin through 2.2.2.0 (a chain-based proof-of-stake cryptocurrency) allows a remote denial of service, exploitable by an attacker who acquires even a small amount of stake/coins in the system. The attacker sends invalid headers/blocks, which are stored on the victim's disk.

    Product
    Cloakcoin
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Oct 15, 2019A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured.CVE-2019-14832 · Other software · keycloak · reported by Red HatHigh 7.5

    A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out further attacks.

    Product
    keycloak REST API
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 14, 2019It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures.CVE-2019-10201 · Other software · Red Hat · reported by Red HatHigh 8.1

    It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 14, 2019It was found that Keycloak's account console, up to 6.0.1, did not perform adequate header checks in some requests.CVE-2019-10199 · Other software · Red Hat · reported by Red HatHigh 8.8

    It was found that Keycloak's account console, up to 6.0.1, did not perform adequate header checks in some requests. An attacker could use this flaw to trick an authenticated user into performing operations via request from an untrusted domain.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 12, 2019A vulnerability was found in keycloak before 6.0.2.CVE-2019-3875 · Other software · Red Hat · reported by Red HatMedium 6.5

    A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path. Keycloak currently doesn't validate signatures on CRL, which can result in a possibility of various attacks like man-in-the-middle.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jun 12, 2019It was found that Keycloak's Node.js adapter before version 4.8.3 did not properly verify the web token received from the server in its backchannel logout .CVE-2019-10157 · Other software · Red Hat · reported by Red HatMedium 4.7

    It was found that Keycloak's Node.js adapter before version 4.8.3 did not properly verify the web token received from the server in its backchannel logout . An attacker with local access could use this to construct a malicious web token setting an NBF parameter that could prevent user access indefinitely.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 24, 2019Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC.CVE-2019-3868 · Other software · Red Hat · reported by Red HatLow 3.8

    Keycloak up to version 6.0.0 allows the end user token (access or id token JWT) to be used as the session cookie for browser sessions for OIDC. As a result an attacker with access to service provider backend could hijack user’s browser session.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 30, 2018The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions.CVE-2018-14637 · Other software · [UNKNOWN] · reported by Red HatMedium 6.1

    The SAML broker consumer endpoint in Keycloak before version 4.6.0.Final ignores expiration conditions on SAML assertions. An attacker can exploit this vulnerability to perform a replay attack.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 13, 2018A flaw was found in JBOSS Keycloak 3.2.1.Final.CVE-2018-14658 · Other software · Red Hat · reported by Red HatMedium 6.1

    A flaw was found in JBOSS Keycloak 3.2.1.Final. The Redirect URL for both Login and Logout are not normalized in org.keycloak.protocol.oidc.utils.RedirectUtils before the redirect url is verified. This can lead to an Open Redirection attack

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 13, 2018A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final.CVE-2018-14657 · Other software · Red Hat · reported by Red HatHigh 8.1

    A flaw was found in Keycloak 4.2.1.Final, 4.3.0.Final. When TOPT enabled, an improper implementation of the Brute Force detection algorithm will not enforce its protection measures.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 13, 2018A flaw was found in Keycloak 3.4.3.Final, 4.0.0.Beta2, 4.3.0.Final.CVE-2018-14655 · Other software · Red Hat · reported by Red HatMedium 4.6

    A flaw was found in Keycloak 3.4.3.Final, 4.0.0.Beta2, 4.3.0.Final. When using 'response_mode=form_post' it is possible to inject arbitrary Javascript-Code via the 'state'-parameter in the authentication URL. This allows an XSS-Attack upon succesfully login.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 1, 2018It was found that SAML authentication in Keycloak 3.4.3.Final incorrectly authenticated expired certificates.CVE-2018-10894 · Other software · Red Hat · reported by Red HatMedium 5.4

    It was found that SAML authentication in Keycloak 3.4.3.Final incorrectly authenticated expired certificates. A malicious user could use this to access unauthorized data or possibly conduct further attacks.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 1, 2018It was found that the keycloak before 2.3.0 did not implement authentication flow correctly.CVE-2016-8609 · Other software · Red Hat · reported by Red HatLow 3.7

    It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 27, 2018It was found that when Keycloak before 2.5.5 receives a Logout request with a Extensions in the middle of the request, the SAMLSloRequestParser.parse() method eCVE-2017-2646 · Other software · Red Hat · reported by Red HatHigh 7.5

    It was found that when Keycloak before 2.5.5 receives a Logout request with a Extensions in the middle of the request, the SAMLSloRequestParser.parse() method ends in a infinite loop. An attacker could use this flaw to conduct denial of service attacks.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 26, 2018It was found that while parsing the SAML messages the StaxParserUtil class of keycloak before 2.5.1 replaces special strings for obtaining attribute values withCVE-2017-2582 · Other software · Red Hat · reported by Red HatMedium 6.5

    It was found that while parsing the SAML messages the StaxParserUtil class of keycloak before 2.5.1 replaces special strings for obtaining attribute values with system property. This could allow an attacker to determine values of system properties at the attacked system by formatting the SAML request ID field to be the chosen system property which could be obtained in the "InResponseTo" field in the response.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 23, 2018keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement.CVE-2018-10912 · Other software · [UNKNOWN] · reported by Red HatMedium 4.9

    keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement. A Keycloak cluster with multiple nodes could mishandle an expired session replacement and lead to an infinite loop. A malicious authenticated user could use this flaw to achieve Denial of Service on the server.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 12, 2018Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially lCVE-2017-2585 · Other software · Red Hat, Inc. · reported by Red HatMedium 5.9

    Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in non-constant time, potentially leaving the application vulnerable to timing attacks.

    Product
    keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Mar 12, 2018Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server.CVE-2016-8629 · Other software · Red Hat, Inc. · reported by Red HatMedium 6.5

    Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Feb 21, 2018It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request.CVE-2017-12161 · Other software · Red Hat, Inc. · reported by Red HatHigh 8.8

    It was found that keycloak before 3.4.2 final would permit misuse of a client-side /etc/hosts entry to spoof a URL in a password reset request. An attacker could use this flaw to craft a malicious password reset request and gain a valid reset token, leading to information disclosure or further attacks.

    Product
    Keycloak
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 19, 2018keycloak-httpd-client-install versions before 0.8 allow users to insecurely pass password through command line, leaking it via command history and process info CVE-2017-15112 · Other software · jdennis · reported by Red HatHigh 7.8

    keycloak-httpd-client-install versions before 0.8 allow users to insecurely pass password through command line, leaking it via command history and process info to other local users.

    Product
    keycloak-httpd-client-install
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jan 19, 2018keycloak-httpd-client-install versions before 0.8 insecurely creates temporary file allowing local attackers to overwrite other files via symbolic link.CVE-2017-15111 · Other software · jdennis · reported by Red HatMedium 5.5

    keycloak-httpd-client-install versions before 0.8 insecurely creates temporary file allowing local attackers to overwrite other files via symbolic link.

    Product
    keycloak-httpd-client-install
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.