
Cloud Vulnerability DB
A community-led vulnerabilities database
In transaction-doctrine from 1.6.0, DoctrineTransactionRunner::forHostEntityManager() detached what a failed run had brought into the host's entity manager, but Doctrine's detach does nothing for an entity in the REMOVED state. When a run loaded an entity, called remove() on it and then failed before the runner's flush (a deadlock, a lock wait timeout, or a domain exception thrown by the closure), the removal stayed scheduled in the host's unit of work after the rollback. The host's next flush(), typically at the end of the same request, then deleted that row even though the operation had failed and been reported as failed. This is data loss. Many nowo-tech bundles run their writes through forHostEntityManager().
Fixed in 1.8.0. After a failed run every scheduled removal of an entity the host did not manage before the run is forgotten entirely (identity map entry, scheduled removal, state, identifier and original data), and the entity is unlinked from the caller's entities like everything else the run brought in.
After a failed run, call clear() on the host's entity manager (or detach the affected entity) before any further flush(), or avoid loading and removing entities inside a run on the host's manager.
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."