{"id":44683,"date":"2022-01-05T22:30:03","date_gmt":"2022-01-05T22:30:03","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/you-better-have-patched-those-log4j-holes-or-well-see-what-a-judge-has-to-say-ftc\/"},"modified":"2022-01-05T22:30:03","modified_gmt":"2022-01-05T22:30:03","slug":"you-better-have-patched-those-log4j-holes-or-well-see-what-a-judge-has-to-say-ftc","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/you-better-have-patched-those-log4j-holes-or-well-see-what-a-judge-has-to-say-ftc\/","title":{"rendered":"You better have patched those Log4j holes or we’ll see what a judge has to say \u2013 FTC"},"content":{"rendered":"

The US Federal Trade Commission on Tuesday warned companies that vulnerable Log4j software needs to be patched \u2026 or else.<\/p>\n

In case any system administrators last month somehow missed the widespread alarm<\/a> over vulnerabilities (CVE-2021-44228<\/a>, CVE-2021-45046<\/a>, CVE-2021-44832<\/a>) in the Java logging package, the trade watchdog said Log4j continues to be exploited by a growing number of attackers and urged organizations to act now before it’s too late.<\/p>\n

The FTC is advising companies to consult the US Cybersecurity and Infrastructure Security Agency’s (CISA) guidance<\/a> on dealing with the Log4j flaws. If companies fail to fix their code and lose customer data, the FTC says it may just see what a judge thinks about that.<\/p>\n