We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
Log4j Breach
After the discovery of the security breach caused by Log4j on the weekend of December 10-12, 2021. We need to know if your software is vulnerable to this security breach.
Hey Bigjoe910 & leksikon - thanks for your patience while we conducted a thorough review of services and components across all Dropbox products.
We have hardened all instances of log4j that were identified on HelloSign and Dropbox-owned platforms by applying a patch or taking other appropriate action. Like many other service providers, we continue to work with our vendors to assess impact and remediation efforts. Our systems are functioning normally and we are not aware of any active threat.
I hope this information helps!
My company is also asking for a status on this - is Dropbox and HelloSign affected?
Walter
Dropbox Staff
Dropbox StaffHey Bigjoe910 & leksikon - thanks for your patience while we conducted a thorough review of services and components across all Dropbox products.
We have hardened all instances of log4j that were identified on HelloSign and Dropbox-owned platforms by applying a patch or taking other appropriate action. Like many other service providers, we continue to work with our vendors to assess impact and remediation efforts. Our systems are functioning normally and we are not aware of any active threat.
I hope this information helps!
Is there any update on if both CVE's related to Log4j are remediated or mitigated on the Dropbox platform? The latest CVE was just added late 12/14/2021.
CVE-2021-45046
CVE-2021-44228Is there any update on if both CVE's related to Log4j are remediated or mitigated on the Dropbox platform? The latest CVE was just added late 12/14/2021.
CVE-2021-45046
CVE-2021-44228Hello everyone
I wrote Dropbox support and received a generic response that they are looking into it and will work the various vendors to work with to provide a safe environment (basically that is what it said); This is disappointing that we need to push the vendor to provide an update to us. TO date (12/21/21) I have not seen a dedicated page on their website for Log4J.
Zee
Hi,
Do you have any update? Could you please confirm how does this affect Dropbox and/or if it has already been mitigated?
Thank you and I look forward to your response.
Kind Regards,
JCarreon
- WalterHi all - thanks for your nudges.
I just wanted to re-iterate that since the incident was originally reported, we have hardened all instances of log4j that were identified on HelloSign and Dropbox-owned platforms by applying a patch and/or taking other appropriate actions.
Just like other service providers, we continue to work with our vendors to assess impact and remediation efforts.
Our systems are functioning normally at the moment and we are not aware of any active threat.
I hope this helps!Hello Dropboxer,
Few observations as I am still marking Dropbox as ORANGE on my tracking list:
A- I can't see what date you are indicating that Dropbox is working with vendors to mitigate the risk? which date does it apply to?
B- Even though on the surface it seems Dropbox has hardened itself you are falling short on stating Dropbox isn't at risk. Where are we on the spectrum of risk say 1 to 5 (5 to be the highest?)
C- When will Dropbox have an official stance on their website and not through a community response like many other vendors? I haven't found one if there is one kindly post the link herein.
Thx,
Z
- MeganHappy Tuesday guys!
As mentioned, we conducted a thorough review of services and components across all Dropbox products.
We hardened all instances of log4j that were identified on Dropbox-owned platforms by applying a patch or taking other appropriate action. Our systems are functioning normally, and we have no evidence that this vulnerability was exploited.
We will continue to work with our vendors to assess the impact and remediation efforts.
So far, our vendors were either not vulnerable or had taken appropriate action. We have not seen any evidence of exploitation at our vendors. We’re still following up with a few vendors, like many other companies.
I hope this clarifies!Howdy, friends!
As a follow-up to the Log4j vulnerability, our IT Security team is asking for the following specifics:- Confirmation that Dropbox is no longer vulnerable (which is already available here in this discussion)
- The vulnerable version Dropbox was using
- The latest version Dropbox patched to (with dates)
Any insight anyone can share is greatly appreciated.
Thank you!
