Question

log4j and DigitalOcean front-end / API etc

Hi DigitalOcean - I know I am not running log4j on my servers in your stack I would like confirmation from DigitalOcean that your systems and front-end etc do not pose access vulnerabilities to my Droplets, Spaces or similar via this vulnerability. Can you put out a statement please? Thanks!


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

Hi there,

In addition to what has already been mentioned, here is a link to DigitalOcean’s response to the Log4j security vulnerability

https://www.digitalocean.com/blog/digitaloceans-response-to-the-log4j-security-vulnerability

Best, Bobby

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hello, @mdgosden

Apache log4j 2 is an open-source Java-based logging framework that should not be installed by default on your Apache server, hence you’ve not manually installed/configured it then CVE-2021-44228 should not affect your server.

The package may be available for install, but if you haven’t installed it manually on your droplet then you should not be affected.

Regards, Alex