CVE-2024-1524
HighSummary
Podatność CVE-2024-1524 dotyczy sytuacji, w której włączona funkcja 'Silent Just-In-Time Provisioning' dla dostawcy tożsamości (IDP) może prowadzić do zastąpienia informacji o użytkowniku lokalnym podczas procesu tworzenia konta. Problem występuje, gdy użytkownicy federacyjni mają tę samą nazwę użytkownika co lokalni użytkownicy.
Risk Assessment
Organizacja może być narażona na ryzyko, że złośliwy aktor skojarzy konto lokalnego użytkownika z kontem użytkownika IDP, co może prowadzić do nieautoryzowanego dostępu do danych lokalnych.
Recommendation
Zaleca się wyłączenie funkcji 'Silent Just-In-Time Provisioning' lub zapewnienie, że nazwy użytkowników lokalnych i federacyjnych są unikalne, aby zminimalizować ryzyko związane z tą podatnością.
Related vulnerabilities
- CVE-2026-15688Critical
A vulnerability in Mitsubishi Electric GX Works3 and Motion Control Setting stems from an incorrect implementation of the authentication algorithm. A local attacker can successfully authenticate even with an invalid block password by modifying part of the executable module in memory.
- CVE-2026-88795Critical
The wpShopGermany IT-RECHT KANZLEI WordPress plugin before 2.4 does not generate its API authentication token securely, deriving it from data the requester controls and creating it as a side effect of the check that is supposed to validate it. This allows unauthenticated attackers to predict the token and use the access it grants to write arbitrary files, leading to remote code execution.
- CVE-2026-86710Critical
The Login with QR WordPress plugin through 1.0.0 does not verify that the code used to log a user in is one it issued, matching any stored user metadata value instead. This allows unauthenticated attackers to log in as any user, including administrators.
- CVE-2026-86709Critical
The Pressengine WordPress plugin through 1.0 does not stop its login handler from issuing a session when authentication fails. This allows unauthenticated attackers to log in as any user, including administrators.
- CVE-2026-86707Critical
The Private Feed Key WordPress plugin through 0.1 does not verify that the key used to authenticate a feed request is one it issued, matching any stored user metadata value instead. This allows unauthenticated attackers to log in as any user, including administrators.
- CVE-2026-87796Critical
The Multi Uploader for Gravity Forms plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to and including 1.1.9 via the move_file function. This is due to insufficient file type validation during chunked upload handling. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
- CVE-2026-61594Critical
djust prior to version 1.0.7 has a vulnerability in the WebSocket transport that bypasses standard Django authorization mechanisms (such as LoginRequiredMixin, PermissionRequiredMixin, etc.) and the staff gate in the admin extension. Mount authorization is done via check_view_auth, not the View.dispatch() chain, allowing anonymous or under-privileged clients to open a WebSocket and dispatch view handlers, including admin ones.
- CVE-2026-92805Critical
UVdesk Community Skeleton through 1.1.8 fails to authenticate or validate installation state on wizard endpoints in ConfigureHelpdesk controller actions. Unauthenticated attackers can repoint the database and create super administrator accounts by submitting crafted requests to wizard endpoints, gaining full control of the instance.
- CVE-2026-92787Critical
Feast through 0.66.0 fails to verify JWT token signatures before establishing user identity, allowing attackers to bypass all role-based access control by presenting an unverified token with a hardcoded claim value. Attackers can obtain trusted internal identity and gain unchecked read and write access to all entities, feature views, data sources, and permission policies on the server.
- CVE-2026-76460CriticalActively exploited
A vulnerability in the API of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to bypass authentication. This is due to insufficient authentication control on an API endpoint. An attacker could send a crafted request to gain unauthorized access to the device by bypassing the web-based management interface.
Original NVD description (English source)
When the "Silent Just-In-Time Provisioning" feature is enabled for a federated identity provider (IDP) there is a risk that a local user store user's information may be replaced during the account provisioning process in cases where federated users share the same username as local users. There will be no impact on your deployment if any of the preconditions mentioned below are not met. Only when all the preconditions mentioned below are fulfilled could a malicious actor associate a targeted local user account with a federated IDP user account that they control. The Deployment should have: -An IDP configured for federated authentication with Silent JIT provisioning enabled. The malicious actor should have: -A fresh valid user account in the federated IDP that has not been used earlier. -Knowledge of the username of a valid user in the local IDP. -An account at the federated IDP matching the targeted local username.