Security Leftovers
-
Linux-friendly email program hit by zero-day bug [Ed: "Linux-friendly": how Microsofters blame on "Linux" things that have nothing to do with it]
Zimbra has issued a warning that its email platform and supporting software are prone to a security glitch that’s being actively exploited by threat actors, a cyber watchdog warned today.
CybersecurityHelp quoted the email services provider on July 17th as saying: “A security vulnerability in Zimbra Collaboration Suite Version 8.8.15 that could potentially impact the confidentiality and integrity of your data has surfaced.”
The bug is fresh enough that it has yet to be assigned a CVE docket number, although Zimbra claims it has patched the system flaw.
-
Security updates for Tuesday [LWN.net]
Security updates have been issued by Fedora (java-1.8.0-openjdk), Red Hat (bind, bind9.16, curl, edk2, java-1.8.0-ibm, kernel, kernel-rt, and kpatch-patch), SUSE (iniparser, installation-images, java-1_8_0-ibm, kernel, libqt5-qtbase, nodejs16, openvswitch, and ucode-intel), and Ubuntu (linux-oem-6.0 and linux-xilinx-zynqmp).
-
No Need to Hack When It’s Leaking.. and Leaking… and Leaking…
In 2022, DataBreaches filed a watchdog complaint with HHS about a leak of patient information. The patient data appeared to be from a Florida nursing services entity and was exposed in an unsecured Amazon bucket. Attempts by multiple entities to alert the Florida firm to the leak were unsuccessful, as outlined in our previous post.
This week, I learned that the entity was telling HHS investigators that they had never been contacted by any of the entities I named in my complaint and that it wasn’t their bucket and maybe I had the wrong entity.
HHS asked me if I could send them evidence to support my claims.
So I started searching thru my files and contacted Jelle Ursem, one of the researchers who had reported discovering that leak and who had called the entity twice trying to disclose responsibly, to no avail. I also contacted Blue Cross Blue Shield and asked if they had logged their phone call to the entity.
-
Phoenician Medical Center notifying 162,500 patients of attack that “disrupted” IT systems
And while Henry Ford Health is notifying 168,000 patients who are possibly affected by a phishing attack, Phoenician Medical Center in Arizona is notifying 162.500 patients about sounds like it may be a ransomware attack although they don’t say exactly what caused the “disruption” in their IT systems on March 31.
Their press release makes no mention of offering patients any mitigation services. Perhaps they are offering services to those who call them, or perhaps they think it’s unnecessary for the types of information that was potentially compromised?
-
CalPERS CEO gives update on data hack that exposed Social Security numbers, birth dates
The California Public Employee and Retirement System launched its three-day offsite meeting in Monterey with a long-awaited update on a June data breach that exposed Social Security numbers, birth dates and other personal information on nearly 1.2 million retirees and other beneficiaries.
The update follows a call from California State Treasurer Fiona Ma, who sits on both the CalPERS and CalSTRS boards, for the nation’s two largest public pension funds to hold special meetings and provide members with an update on the organization’s response to the breach.
-
Henry Ford Health confirms data breach affecting 168,000 patients
Henry Ford Health has confirmed that an email phishing scheme led to a data breach affecting 168,000 patients.
Patients were told Monday that someone conducting an email phishing scheme gained access to business email accounts on March 30, 2023. That access was quickly discovered, and the email accounts were secured, according to officials.
Some patient information was contained in the affected emails, but it’s unclear if that information was accessed, according to Henry Ford Health. This discovery was made on May 16. The affected information might have included name, gender, date of birth, age, lab results, procedure type, diagnosis, date of service, telephone number, medical record number and/or internal tracking number.