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 Sep 9 2025: p1 security update
Announcing Java updates of Jul 15, 2025 for 8, 11, 17, 21, and 24: thoughts and resources
Announcing ColdFusion updates released July 8 2025: p1 security update and more
Presenting "Debugging & Error Handling in ColdFusion" today, online for CF DevWeek
Announcing ColdFusion updates released May 13 2025: p1 security update (and more)
How to disable the Asus NumberPad, embedded within touchpad on some modern laptops
Charlie Arehart said:
Yep. Thanks for that, Jim.
How to disable the Asus NumberPad, embedded within touchpad on some modern laptops
Jim said:
I have an Asus ROG Strix with the extra software of Armoury Crate for advanced settings. When I go
...
[more]
Announcing ColdFusion updates released Sep 9 2025: p1 security update
Charlie Arehart said:
The auto (admin) update really can and does work every time for many. Whenever it doesn
...
[more]
Announcing ColdFusion updates released Sep 9 2025: p1 security update
Tony Mason said:
amazingly, the automatic update actually worked for the first time in ....ever? However, I for
...
[more]
ColdFusion 2025 released, Feb 25 2025: resources and my initial thoughts
Future former customer said:
Thanks you very much for replying, Charlie, and I realize of course that you're not defending A
...
[more]
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.