Live data from Hacker News

CISA Director on Log4j Vulnerability

cisa.gov

11–20 of 85 posts

Re: CISA Director on Log4j Vulnerability

#11
post #7

“we are also convening a national call with critical infrastructure stakeholders on Monday afternoon” Shouldn’t this be happening, like, yesterday?

Do not worry, because:

> We have established a JCDC senior leadership group to coordinate collective action and ensure shared visibility into both the prevalence of this vulnerability and threat activity

Very clearly they know what they will be doing.

Re: CISA Director on Log4j Vulnerability

#15
post #13
post #8

do I need to worry about this as a frontend web developer?

Do you have any java in your application stack (i.e. elastic search)? If there’s no java, then there’s no log4j and you may worry about other issues.

*are you using ElasticSearch, flink, spark, prest,…etc. do they read in user data supplied by your front end. Could this user data end up being logged intentionally or part of an error log output. If so, you might be vulnerable and should update those systems.

Re: CISA Director on Log4j Vulnerability

#16
post #14

Someone should tell them that any system that it logging user supplied data can be affected. Not only "user facing" systems. Not even a WAF can protect these.

If the WAF blocks any request containing "{", that would be fairly safe, right?

Yes, some attacks could still get through (e.g. a backend that receives requests base64-encoded), but that's the case generally with WAFs I think.

Re: CISA Director on Log4j Vulnerability

#17
post #7

“we are also convening a national call with critical infrastructure stakeholders on Monday afternoon” Shouldn’t this be happening, like, yesterday?

No. The stakeholders are busy patching their shit. Pulling folks into meetings shouldn't be the priority when teams around the world in virtually every tech organizations are in firefighting mode.

This type of a call would likely be focused on assessing current state at that point.

Re: CISA Director on Log4j Vulnerability

#18
post #7

“we are also convening a national call with critical infrastructure stakeholders on Monday afternoon” Shouldn’t this be happening, like, yesterday?

Security vulnerabilities aren’t exploited on weekends out of courtesy

I always deeply appreciated this strict code of honour in the 'industry'. But one should take care of what constitutes the workweek here: https://en.wikipedia.org/wiki/Workweek_and_weekend

Re: CISA Director on Log4j Vulnerability

#19
post #16
post #14

Someone should tell them that any system that it logging user supplied data can be affected. Not only "user facing" systems. Not even a WAF can protect these.

If the WAF blocks any request containing "{", that would be fairly safe, right? Yes, some attacks could still get through (e.g. a backend that receives requests base64-encoded), but that's the case generally with WAFs I think.

Thag would also mean blocking any apis that use json. This would not end well in the short term, or long term.

Re: CISA Director on Log4j Vulnerability

#20
post #7

“we are also convening a national call with critical infrastructure stakeholders on Monday afternoon” Shouldn’t this be happening, like, yesterday?

Security vulnerabilities aren’t exploited on weekends out of courtesy

Unfortunately NSO group likely has a different definition of weekend.
Post reply on HN