Closed (fixed)
Project:
Entity cache
Version:
7.x-1.5
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
25 Jun 2018 at 18:03 UTC
Updated:
19 Jul 2023 at 10:17 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
MPetrovic commentedPatch to fix deprecation attached.
Comment #3
herved commented+1
Thanks for the patch. It looks good to me.
Comment #4
gregglesA patch needs review.
Comment #6
gregglesI don't understand those test run results :/
Comment #7
MPetrovic commentedNeither do I. Build successful, all tests passed, failed testing, build failed?
Comment #8
herved commentedI think there's an issue with the testbot ATM. I noticed this in another contrib issue (context).
I believe this is the related issue: #2990645: "Build Successful" is treated as a test failure
They may have fixed it a few hours ago. Let's try a retest...
Comment #9
herved commentedSo the testbot seems to be working again, all tests passed here.
Switching back to needs review.
Comment #10
smazI've just tested the patch in #2, and all works ok - after using drush to clear both a specific entity table + all caches, the relevant tables were cleared.
It also clears the warning being generated by PHPCodesniffer.
As above, the tests appeared to be ok so marking this as RTBC.
Comment #12
catchCommitted/pushed to 7.x-1.x, thanks!
Comment #14
harlor commentedDamn I guess I'm too late to fix the typo in lamdba :S
Comment #15
ressaThanks for fixing this. Since more and more sites are using PHP 8, could a fresh release be considered at some point?
Comment #16
philsward commented+1 for an updated release to fix this issue.
Comment #17
mcdruid commentedThere's an issue about a 7.x-1.6 release #3002960: Issues to fix as part of next stable release (7.x-1.6).
The presence of
create_function()in the current release could be exploited to gain Remote Code Execution although the conditions for this to happen are pretty extreme / unlikely. It could represent part of a chained attack though.I filed a private security issues about this a long time ago and it was agreed that the discussion could take place in public.
I won't put the exact details here just yet as the "vulnerable" code is still in the latest supported release.