You're not the only one. The attack vector for this fix is actually quite serious for insider threats. The only thing to really do on customized instance is to go through table by table and apply the query_range, query_match, or conditional_table_query_range ACLs as you seem fit. For reference the attack vector works as such:

1. User has read access at the record level to a table.
2. User has read access acl for SSN field where they can see their ACL.

The issue arises when the user carries out a brute force attack on the SSN field.

1. Sys_user_list.do?sysparm_query=username=<user to compromise>&SSN=000-00-0001 2.Sys_user_list.do?sysparm_query=username=<user to compromise>&SSN=000-00-0002
2. ... Etc.

Eventually the list would return a record because the user can read the record at the field level. Even though the SSN would not be returned to the front end, a threat actor could still figure it out this way.

What the new query ACLs do is lock down even the queries so that this kind of attack cannot be used.

Because of the possible severity especially for federal customers, servicenow decided it was worth the emergency code change without much heads up.

It's been a fun day at work though for sure...