Snyk Security Database

@platform-services/hrm-mfe-core is a malicious package. This package contains malicious code, and its content was removed from the official package manager. While this package might be attempting to impersonate a valid organization, there is no connection between that organization and this package authorship.

apache-airflow-providers-amazon is a Provider for Apache Airflow. Implements apache-airflow-providers-amazon package

Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF) via the AWS auth manager SAML login flow, where login() discards the AuthnRequest id generated by saml_auth.login() and login_callback() calls process_response() with no request_id. Because python3-saml only validates the InResponseTo field when an id is explicitly supplied, the check is skipped entirely, allowing any SAML assertion signed by the configured IdP to be accepted - including one obtained from a login flow initiated by a different browser. An attacker who can obtain a valid IdP-signed assertion (for example, by initiating their own login and capturing the response) can replay it in a victim's browser session to authenticate as the assertion's subject.

Note: This is only exploitable when the attacker can obtain a valid SAML assertion signed by the configured IdP and present it to the callback endpoint of a different browser session.

Affected versions of this package are vulnerable to Out-of-bounds Read in the decodeChunk method of UnsafeChunkDecoder, which resolves back references and copies literal runs through sun.misc.Unsafe without confirming that a back reference lands at or after the start of the output region, or that a literal run near the end of the input lies within the input array. An attacker can read memory outside both arrays into the decompressed result, and crash the JVM, by supplying LZF data whose back reference offset points before the first byte written or whose trailing literal run extends past the end of the compressed input, since Unsafe accesses carry no bounds checking. This requires the application to decompress LZF data from a source it does not control and the Unsafe based decoder to be the one in use.