Since Apache Kafka 3.0.0, users are allowed to specify these properties in connector configurations for Kafka Connect clusters running with out-of-the-box configurations. Attacker can cause unrestricted deserialization of untrusted data (or) RCE vulnerability when there are gadgets in the classpath. This will allow the server to connect to the attacker's LDAP server and deserialize the LDAP response, which the attacker can use to execute java deserialization gadget chains on the Kafka connect server. When configuring the connector via the Kafka Connect REST API, an authenticated operator can set the `` property for any of the connector's Kafka clients to ".module.JndiLoginModule", which can be done via the `.config`, `.config`, or `.config` properties. This requires access to a Kafka Connect worker, and the ability to create/modify connectors on it with an arbitrary Kafka client SASL JAAS config and a SASL-based security protocol, which has been possible on Kafka Connect clusters since Apache Kafka 2.3.0. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-086.Ī possible security vulnerability has been identified in Apache Kafka Connect. Although a `RestrictedObjectInputStream` is in place, that puts some restriction on what classes can be deserialized, it still allows a broad range of java packages and potentially exploitable with different gadget chains. This issue may lead to Remote Code Execution (RCE) in the worst case. Specifically, if any of the id_token claims value start with the prefix, pac4j considers the value to be a serialized Java object and will deserialize it. The processing of the `id_token` is done in an unsafe manner which is not properly accounted for by the DataHub frontend. When the DataHub frontend is configured to authenticate via SSO, it will leverage the pac4j library. This vulnerability was discovered and reported by the GitHub Security lab and is tracked as GHSL-2022-081.ĭataHub is an open-source metadata platform. There are no known workarounds for this issue. As a result of this issue unauthenticated users may gain access to the system. The reason for this is that while an error is thrown in the `authenticateJaasUser` method it is swallowed without propagating the error. In the event a system is using Java Authentication and Authorization Service (JAAS) authentication and that system is given a configuration which contains an error, the authentication for the system will fail open and allow an attacker to login using any username and password. DataHub is an open-source metadata platform.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |