Back to bug 2081484
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Anten Skrabec | 2022-05-03 21:20:31 UTC | Depends On | 2081485 | |
| Anten Skrabec | 2022-05-03 21:20:42 UTC | CC | bbuckingham, bcourt, btotty, ehelms, jsherril, lzap, mhulan, mmccune, myarboro, nmoumoul, orabin, pcreech, rchan | |
| Anten Skrabec | 2022-05-03 21:30:45 UTC | Depends On | 2081490, 2081489 | |
| Chess Hazlett | 2022-05-03 21:59:26 UTC | CC | aboyko, boliveir, chazlett, drieden, jochrist, jwon, krathod, loleary, pdrozd, pjindal, pskopek, spinder, sthorger, theute | |
| Chess Hazlett | 2022-05-03 22:18:47 UTC | Fixed In Version | liquibase 4.8.0 | |
| Red Hat Bugzilla | 2022-07-18 09:51:41 UTC | CC | mmccune | |
| Red Hat Bugzilla | 2022-10-28 13:12:37 UTC | CC | krathod | |
| Red Hat Bugzilla | 2022-12-31 23:43:23 UTC | CC | aboyko | |
| Chess Hazlett | 2023-02-16 18:33:22 UTC | Doc Text | Liquiibase's XMLChangeLogSAXParser() function uses SAXParser with no FEATURE_SECURE_PROCESSING set, which could possibly allow XXE attacks. | |
| Paige Jung | 2023-02-16 19:36:49 UTC | Doc Text | Liquiibase's XMLChangeLogSAXParser() function uses SAXParser with no FEATURE_SECURE_PROCESSING set, which could possibly allow XXE attacks. | A flaw was found in Liquiibase's XMLChangeLogSAXParser() function. It uses SAXParser with no FEATURE_SECURE_PROCESSING set, which could possibly allow XML External Entity (XXE) attacks. |
| Red Hat Bugzilla | 2023-03-02 08:27:30 UTC | CC | myarboro | |
| Red Hat Bugzilla | 2023-05-15 18:09:29 UTC | CC | drieden | |
| Red Hat Bugzilla | 2023-05-15 20:18:50 UTC | CC | btotty | |
| Red Hat Bugzilla | 2023-07-07 08:32:48 UTC | Assignee | security-response-team | nobody |
Back to bug 2081484