Announcing CF update released Jul 14 2023: a second priority 1 security update in one week
For more on the update, and some additional thoughts, read on.
For more on the update, and some additional thoughts, read on.
Announcing ColdFusion updates released May 13 2025: p1 security update (and more)
Presenting "Solving Common Problems with CF Updates" today, online
Announcing Java updates of Apr 15, 2025 for 8, 11, 17, 21, and 24: thoughts and resources
Delighted to be speaking at Into the Box 2025, in early May
Presenting "Hidden Gems in CF2025" at CF Summit East in March, CFCamp in May
Announcing ColdFusion updates released May 13 2025: p1 security update (and more)
Charlie Arehart said:
First, thanks for the kind regards. Second, yes, the update itself "worked" (thus the new
...
[more]
Announcing ColdFusion updates released May 13 2025: p1 security update (and more)
Paul said:
Otherwise, all REST APIs now seem to be running with no effect from the new update.
We did have a c
...
[more]
Announcing ColdFusion updates released May 13 2025: p1 security update (and more)
Charlie Arehart said:
My guess (from this info alone) would be that the implementation of updated packages had trouble. Th
...
[more]
Announcing ColdFusion updates released May 13 2025: p1 security update (and more)
Paul said:
We had a test server updated and afterward, every site was throwing this error:
"Cannot find i
...
[more]
Announcing ColdFusion updates released May 13 2025: p1 security update (and more)
Charlie Arehart said:
Thanks, Paul. Yes, it will be interesting to hear (whether from you or anyone who may try sooner).
I will note that while that post indicates that "There is currently no mitigation", that may not be the final/complete answer. Note how it refers to the _cfclient querystring, and notice that in my first post last week (on the Jul 11 CF update), I did point out how my March blog post on the previous CF update discussed ways to BLOCK ALL REQUESTS using that _cfclient querystring. I also elaborate there on what it's about, how one can determine if they may have any legit use of it (most do not), and much more. See https://www.carehart...
As I've said elsewhere, it's just not clear how many of the recently closed vulns DO work based on the _cfclient querystring. That post is about all we have to go on, as I've not seen any others. While those on cf2018 and above can apply these fixes to address what Adobe has found, it's just not clear (for now) what those on cf2016 can or should do, other than block requests with that querystring.