Headline
GHSA-9623-mj7j-p9v4: Quarkus potentially leaks data when duplicating a duplicated context
Impact
Vert.x 4.5.12 has changed the semantics of the duplication of duplicated context.
Duplicated context is an object used to propagate data through a processing (synchronous or asynchronous). Each “transaction” or “processing” runs on its own isolated duplicated context.
Initially, duplicating a duplicated context was creating a fresh (empty) new context, meaning that the new duplicated context can be used to managed a separated transaction.
In Vert.x 4.5.12, this semantics has changed, and since the content of the parent duplicated context is copied into the new one, potentially leaking data.
This CVE is especially for Quarkus as Quarkus extensively uses the Vert.x duplicated context to implement context propagation. With the new semantic data from one transaction can leak to the data from another transaction. From a Vert.x point of view, this new semantic clarifies the behavior.
A significant amount of data is stored in the duplicated context, including request scope, security details, and metadata. Duplicating a duplicated context is rather rare and is only done in a few places:
- Quarkus REST Client when using OTel (but it’s the same transaction, so no leak)
- Quarkus Messaging connectors
- Quarkus SmallRye Health (same transaction, so no leak)
Patches
After discussion with the Vert.x team, the change will be rolled back in Vert.x 4.x. A new API will be added to Vert.x 5 do distinguish the 2 cases.
Workarounds
When duplicating a duplicated context, the following code can be done to avoid the potential leak:
((ContextInternal) VertxContext.getRootContext(ctx)).duplicate()
This workaround would not be required once the Vert.x version containing the fix will be included. Note that the workaround would still work.
References
This issue have been reported in https://github.com/quarkusio/quarkus/issues/48227.
Impact
Vert.x 4.5.12 has changed the semantics of the duplication of duplicated context.
Duplicated context is an object used to propagate data through a processing (synchronous or asynchronous). Each “transaction” or “processing” runs on its own isolated duplicated context.
Initially, duplicating a duplicated context was creating a fresh (empty) new context, meaning that the new duplicated context can be used to managed a separated transaction.
In Vert.x 4.5.12, this semantics has changed, and since the content of the parent duplicated context is copied into the new one, potentially leaking data.
This CVE is especially for Quarkus as Quarkus extensively uses the Vert.x duplicated context to implement context propagation. With the new semantic data from one transaction can leak to the data from another transaction. From a Vert.x point of view, this new semantic clarifies the behavior.
A significant amount of data is stored in the duplicated context, including request scope, security details, and metadata. Duplicating a duplicated context is rather rare and is only done in a few places:
- Quarkus REST Client when using OTel (but it’s the same transaction, so no leak)
- Quarkus Messaging connectors
- Quarkus SmallRye Health (same transaction, so no leak)
Patches
After discussion with the Vert.x team, the change will be rolled back in Vert.x 4.x. A new API will be added to Vert.x 5 do distinguish the 2 cases.
Workarounds
When duplicating a duplicated context, the following code can be done to avoid the potential leak:
((ContextInternal) VertxContext.getRootContext(ctx)).duplicate()
This workaround would not be required once the Vert.x version containing the fix will be included. Note that the workaround would still work.
References
This issue have been reported in quarkusio/quarkus#48227.
References
- GHSA-9623-mj7j-p9v4
- quarkusio/quarkus#48227
- quarkusio/quarkus@2b58f59