@4Dgifts I think "enshittification" is the right word: https://packetstorm.news/view/36662 (yes, this is the new domain apparently)

LinkedIn's cookie banner got to the point where I can't use the site at all. Not that I want to, but still pretty awkward...

UPDATE: #ESETresearch was contacted by one of the possible authors of the Bootkitty bootkit, claiming the bootkit is a part of project created by cybersecurity students participating in Korea's Best of the Best (BoB) training program. 1/2
https://www.welivesecurity.com/en/eset-research/bootkitty-analyzing-first-uefi-bootkit-linux/

Perl interpreter patch to issue runtime warnings against suspicious two-argument open() calls https://www.openwall.com/lists/oss-security/2024/12/04/1

SonicWall security advisory 03 December 2024: SonicWall SMA100 SSL-VPN Affected By Multiple Vulnerabilities

• CVE-2024-38475 (7.5 high) Path traversal vulnerability – attributed to publicly known Apache HTTP Server vulnerability
• CVE-2024-40763 (7.5 high) SonicWALL SMA100 Heap-based buffer overflow vulnerability
• CVE-2024-45318 (8.1 high) Stack-based buffer overflow vulnerability
• CVE-2024-45319 (6.3 medium) Certificate-based authentication bypass
• CVE-2024-53702 (5.3 medium) Insecure randomness 🤪
• CVE-2024-53703 (8.1 high) Stack-based buffer overflow vulnerability

There is no evidence that these vulnerabilities are being exploited in the wild

#sonicwall #sma #sslvpn #vulnerability #CVE #infosec #cybersecurity

To boost @ciaranmak:

Is there an archive of Packet Storm's data available somewhere?

RE: https://mastodon.ie/@ciaranmak/113600017990303470

[RSS] Where There's Smoke, There's Fire - Mitel MiCollab CVE-2024-35286, CVE-2024-41713 And An 0day

https://labs.watchtowr.com/where-theres-smoke-theres-fire-mitel-micollab-cve-2024-35286-cve-2024-41713-and-an-0day/

R.I.P. Packet Storm :,(

@sigabrt @yeswehack This issue was assigned CVE-2024-52531. While the CVE description states that the vulnerability cannot be reached from the network, it seems, in fact, possible (check the blogpost for details).

Team member @sigabrt describes a fuzzing methodology he used to find a heap overflow in a public @yeswehack bug bounty program for Gnome: https://offsec.almond.consulting/using-aflplusplus-on-bug-bounty-programs-an-example-with-gnome-libsoup.html

Here is a new #NameThatWare challenge.

Please don't just guess into the blue, try to deduct what it is, write down your observations and thoughts.
Hide your answer behind a CW to not spoil it for other participants.

Any recommendations for analog #electronics time-domain simulation software for hobbyists? GUI is a must, support for tubes is a major plus. Primary use-case would be low-frequency signal generation circuits.

@HalvarFlake The link doesn't show up properly (Bsky x-poster bug?)

New Project Zero issue:

Windows Kernel double-fetch in the loading of remote registry hives, leading to memory corruption

https://project-zero.issues.chromium.org/issues/42451731

CVE-2024-43452

As @daringfireball writes, Google is lying through its corporate teeth about its claims to be encrypting messages.

https://daringfireball.net/linked/2024/12/04/shame-on-google-messages

What a slimy company Google has become, so far distant from its early days when it was so admirable.

‼️ New vulnerabilities have been disclosed in the Veeam Service Provider Console.

CVE-2024-42448 is critical, potentially allowing remote code execution. CVE-2024-42449 is rated high, potentially leaking the NTLM hash of a service account & allowing file deletion.

Learn more and see how to find potentially impacted systems:

https://www.runzero.com/blog/veeam-instances/

@floyd @swapgs yeah, I did a quick test and ports should even come back as filtered and >0 hosts up with -Pn.

I updated the diagram representing the different Point and Print configurations and their exploitation on my blog.

Hopefully, this should provide a better understanding of the whole "PrintNightmare" situation to both defenders and red teamers. 🤞

New blog: Risk talk at JPL

Before Thanksgiving, I was in Southern California, and I was honored to be able to give a talk at the Jet Propulsion Lab. The talk is titled “Threat Modeling: Engineering and Science.” The first part of the talk puts threat modeling in context for engineering secure systems, while the second part considers why we do what we do and asks some questions about how we think about risk.

(1/4 https://shostack.org/blog/risk-talk-at-jpl/