9 results · Clear filters · Feed
-
Medium 6.7
Improper Input Neutralization in Okta Access Gateway SNMP Configuration Processing
The Okta Access Gateway does not neutralize shell metacharacters in SNMP configuration values before a privileged script uses them to construct OS commands. An authenticated local user with access to the management interface can supply crafted values, resulti…
-
Medium 5.9
Improper Path Validation in Okta Access Gateway Kerberos Configuration Handling
The Okta Access Gateway Kerberos configuration handler does not validate file paths specified in event payloads before writing file contents. The path from the event payload is used directly as the write destination, resulting in files being written to uninte…
-
Medium 6.8
Improper Input Sanitization in Okta Access Gateway LDAP Datastore Filter Interpolation
The Okta Access Gateway does not sanitize SAML assertion attribute values before interpolating them into LDAP search filters in the LDAP datastore configuration. The raw values are substituted directly into the filter string and passed to the LDAP search oper…
-
Medium 6.7
Insufficient Validation of Dashboard Application Labels in Okta Access Gateway Dashboard Site Configuration
The Okta Access Gateway does not sanitize dashboard label values before writing them into generated PHP configuration files. The generated file is automatically included during authentication requests, resulting in execution with the privileges of the web ser…
-
Medium 4.9
Improper Path Validation in Okta Access Gateway Backup and Restore Functionality
The Okta Access Gateway backup restore function does not validate the filename embedded in an encrypted backup payload. This results in writing file contents to unintended locations on the appliance filesystem.
-
Medium 4.8
Improper Authentication Validation in Okta Access Gateway Pass-Through Authentication Source
The Okta Access Gateway includes an optional pass-through authentication source that accepts user identity from a client-supplied HTTP header without cryptographic validation. In architectures where this optional source is enabled without an upstream reverse …
-
Medium 6.0
Validation Bypass in Okta Access Gateway Custom Directives
The Okta Access Gateway does not apply its Lua directive restriction to the application-level custom configuration field. The field is interpolated directly into the nginx server block without inspection, resulting in execution of injected directives.
-
Medium 6.6
Improper Input Handling in Okta Access Gateway Management Console Exception Handler
The Okta Access Gateway management console passes user-supplied input to eval() without sanitization during an authenticated administrator SSH session. As a result, the unsanitized input is executed directly, leading to code execution with the privileges of t…
-
Medium 6.6
Improper Input Sanitization in Okta Access Gateway Application Label Configuration
The Okta Access Gateway does not sanitize the application label field before including it in the generated nginx configuration file. The unsanitized value is interpolated into an nginx server block directive, resulting in execution of injected directives.