Defined in 2 files
Last patched
pi_next_pcrl in uclouvain/openjpeg was changed by 4 published CVE fixes between 2018 and 2019, in 4 distinct patches that added or removed 68 lines in total.
The name occurs in 2 files: src/lib/openmj2/pi.c, src/lib/openjp3d/pi.c.
uclouvain/openjpeg has 31 CVEs with a located fix in total, so 13% of them touched this function.
Every published CVE whose fix changed pi_next_pcrl, newest first, with the lines each fix touched.
CVE-2018-20847 · src/lib/openjp3d/pi.c · lines 340–347 · +8 −0
CVE-2018-20847 · src/lib/openmj2/pi.c · lines 348–384 · +12 −0 in 2 hunks
CVE-2018-20846 · src/lib/openjp3d/pi.c · lines 340–347 · +8 −0
CVE-2018-20846 · src/lib/openmj2/pi.c · lines 348–384 · +12 −0 in 2 hunks
CVE-2018-20845 · src/lib/openjp3d/pi.c · lines 340–347 · +8 −0
CVE-2018-20845 · src/lib/openmj2/pi.c · lines 348–384 · +12 −0 in 2 hunks
CVE-2018-14423 · src/lib/openjp3d/pi.c · lines 340–347 · +8 −0
Get an alert when the next CVE fix lands in uclouvain/openjpeg, with the patched functions.
Monitor openjpeg CVEsFunctions in the same files that CVE fixes also changed.
Functions in uclouvain/openjpeg changed by the most CVE fixes.
Common questions about CVE fixes to pi_next_pcrl.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
