security: replace unsafe YAML loading with safe_load to prevent RCE #483
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation in okta/okta_configuration.py utilizes yaml.load with potentially
unsafe loaders, which is vulnerable to arbitrary code execution during deserialization of
untrusted YAML input.
Technical Root Cause:
Unsafe loaders (like yaml.Loader or yaml.CLoader) allow the instantiation of any Python object,
providing a direct vector for Remote Code Execution (RCE). Automated analysis has flagged this as
a critical security risk when processing configuration files.
Changes:
only.
This hardening measure eliminates a critical attack vector and aligns the SDK with modern security
standards for data serialization.