Log4j: An Update On “LogJam”
Periodically, serious flaws are exposed in common software infrastructure that’s used everywhere. Once the flaw is discovered, vendors such as MarkLogic have to figure out what the impact is, who might be affected, and notify them as quickly as possible.
This time, the flaw emerged in a widely used error-logging Java library – Log4j. Theoretically, an attacker could execute remote code, which makes it serious.
The Log4j library is not used directly in the MarkLogic server itself, so database security is not affected. However, Log4j is used in our customers’ environments, especially as part of a managed cluster on AWS, hence quite important.
The quick summary can be found here in our KnowledgeBase, with full instructions to determine whether your environment is impacted.
Thank you again for being a MarkLogic customer, and giving us the opportunity to serve you!
Does this flaw impact the security of the MarkLogic database?
No, it does not. However, it potentially might lead to an intrusion within the environment that the database runs in, so it should be considered serious.
Are there new versions – or other remediations – available for the affected environmental components?
Yes. Please contact MarkLogic support if you think you are affected.
Are there any reported intrusions?
No, not at this time, but this is a serious flaw that is likely to be exploited before long.