AAlker955411 (Community Member) asked a question.
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the community.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png){kind=logo}
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Hello @AAlker955411 (Community Member) ,
Veracode is aware of this issue and the blog Analysis and Remediation Guidance to the Log4j Zero-Day RCE (CVE-2021-44228) Vulnerability has been written to aid our customers with the new Log4J zero-day vulnerability.
Please review this blog as it outlines more info on Log4j and remediation advice as well.
Jason
Veracode Support Engineer
Jason,
Thanks for pointing me to a helpful documentation for looking at Log4j issues in our environment... however that doesn't address my initial question. I was specifically asking about log4j issues */IN YOUR APPLIANCE/*.
I posted this too quickly, should have proofread better. I have since identified a couple of issues with my post:
1) Typo'd CVE in title. Should be CVE-2021-44228, rather than CVE-2021-11228
2) The log4j instances I was seeing are version 1.x, rather than 2.x. So they are 5+ years end of life, and affected by CVE-2019-17571
Thanks!