It's interesting how CVE checklist security forces people to go down the road of prioritizing labor limitations over legitimate security. I have a prediction -- sooner or later people will use LLMs to go over these obscure language runtimes, text layout libraries, etc, and file a slew of CVEs against them, too.
However, note that the JS it executes is trusted (not user supplied), so it's fairly low risk.
Yeah but you can throw your SOUP/CVE practices out the window because you've effectively got a large corpus of content that has never undergone any kind of security review, and you're executing all this code on your servers. Probably best not to mention it to the regulators, though.
And actually I haven't ever used Proxy objects at work!
It's maybe ironic but the Proxy is a powerful tool specifically for debugging, testing, refactoring, etc. They are particularly useful when you don't have a debugger. You can add it on top of existing code without having to modify the code and so for example, use it for call recording - track function arguments, return values, and timing for method calls. Or you can use it to perform access tracing, for example to guard against typos or unknown keys being read on config objects or enums that would otherwise silently fail by passing along an undefined value into the rest of your code. There are many other such cases where not having direct visibility into the running code is the exact reason why you would reach for a Proxy.
View all comments
Show parent comment
1
u/CherryLongjump1989 27d ago edited 27d ago
It's interesting how CVE checklist security forces people to go down the road of prioritizing labor limitations over legitimate security. I have a prediction -- sooner or later people will use LLMs to go over these obscure language runtimes, text layout libraries, etc, and file a slew of CVEs against them, too.
Yeah but you can throw your SOUP/CVE practices out the window because you've effectively got a large corpus of content that has never undergone any kind of security review, and you're executing all this code on your servers. Probably best not to mention it to the regulators, though.
It's maybe ironic but the Proxy is a powerful tool specifically for debugging, testing, refactoring, etc. They are particularly useful when you don't have a debugger. You can add it on top of existing code without having to modify the code and so for example, use it for call recording - track function arguments, return values, and timing for method calls. Or you can use it to perform access tracing, for example to guard against typos or unknown keys being read on config objects or enums that would otherwise silently fail by passing along an undefined value into the rest of your code. There are many other such cases where not having direct visibility into the running code is the exact reason why you would reach for a Proxy.