Fluid Attacks News logo

News

Subscribe to Updates

Labels

  • All Posts
  • Fix
  • Announcement
  • Improvement
  • new

Jump to Month

  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • July 2019
Fix
4 years ago

About Integrates massive mailing on 2020-09-20

What happened

  • Last Friday (September 20th) there was an incident in which emails about accepted findings were massively sent.
  • We are currently finishing the implementation of the functionality which allows setting a time limit for the acceptation of findings on the platform.
  • The final step of this functionality is to assign a maximum time of three months to all existing findings that have already been accepted. In the process of performing the latter, due to a programming error, the acceptation emails were sent again and multiple times.
  • The programming mistake that was made allowed the script that updates the acceptation dates of findings to be executed repeatedly and without notice from a development workstation.

What we’ve done

  • As of today (September 23rd), the programming errors have been solved and the emails will not be sent again in this process.
  • To avoid future occurrences of this type, we have restricted the credentials that we used to send all the emails, so now a double check is needed to send any of them.

What’s the impact

  • Approximately 100,000 emails were sent to customers. The users that were affected the most were those who had several projects with assumed findings, receiving up to 1100 emails.
  • No finding that had not previously been accepted was modified, nor were their justification and treatment manager modified.

What we are doing to help
With this announcement, customers are being notified that this does not represent a security threat and was only an internal error.

Avatar of authorJuan