
Cloud Vulnerability DB
A community-led vulnerabilities database
In transaction-doctrine from 1.3.0, when a WriteUnit attempt failed with a transient conflict (deadlock, lock wait timeout, serialization failure) and was replayed, every open entity manager was cleared between attempts unless the unit was scoped with forManagers(), the host application's default manager included. Every entity the host had loaded before run() was detached, even when the unit itself wrote only through DBAL. Changes the host made to those entities afterwards were no longer tracked, so its next flush() silently wrote nothing for them, while the request still reported success. Bundles and applications that use WriteUnit together with the default entity manager are affected.
1.8.0 no longer clears an open manager, and restores it when the failure leaves it open (for example a failure at commit time, in a later statement, or a lock wait timeout after the flush). But when the failure happens inside the attempt's own flush() — the usual case for a deadlock on MySQL and MariaDB — Doctrine closes the entity manager and transaction-doctrine resets it before the replay. Entities the host loaded before run() are then detached, and writes to them are still silently lost in 1.8.0 and 1.8.1. The same happens in 1.8.1 when code inside the attempt clears the manager or detaches every host entity it held. A complete fix (re-attaching the host's entities to the reset manager) is planned for 1.8.2; this advisory will be updated when it is released.
Partially fixed in 1.8.0 (see the update above). An open manager that managed entities before the first attempt is no longer cleared: it is put back to what the database holds (host entities deleted by the attempt are managed again, the attempt's unflushed work is dropped, entities the attempt brought in are unlinked and detached, touched host entities are reloaded without cascading). When a host entity cannot be brought back, the unit gives up with a ConcurrencyConflict (HTTP 409, Retry-After, CONFLICT_001).
Load again, inside the unit's closure, every entity you change in the unit, instead of using entities loaded before run(); this works on every version. Scoping write units with forManagers() to the managers they actually write through also avoids clearing unrelated managers.
Source: NVD
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."