Read Time:1 Second
Post Content
Yearly Archives: 2024
GLSA 202411-09: Perl: Multiple Vulnerabilities
Microsoft Windows NTLMv2 Hash Disclosure Spoofing Vulnerability
Read Time:43 Second
What is the Vulnerability?Microsoft Windows contains an NTLMv2 hash spoofing vulnerability (CVE-2024-43451) that could result in disclosing a user’s NTLMv2 hash to an attacker via a file open operation. The attacker can leverage this hash to impersonate that user with minimal interaction from the victim. This vulnerability (CVE-2024-43451) has been added to CISA’s Known Exploited Vulnerabilities Catalog (KEV) list on November 12, 2024.What is the recommended Mitigation?Microsoft has released a security update to fix the vulnerability on November 12, 2024. https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43451 What FortiGuard Coverage is available?FortiGuard recommends users to apply the fix provided by the vendor as soon as possible.FortiGuard IPS protection is available, and Fortinet customers remain protected through it.The FortiGuard Incident Response team can be engaged to help with any suspected compromise.
Friday Squid Blogging: Female Gonatus Onyx Squid Carrying Her Eggs
Read Time:6 Second
Fantastic video of a female Gonatus onyx squid swimming while carrying her egg sack.
Palo Alto Networks Confirms New Zero-Day Being Exploited by Threat Actors
Read Time:6 Second
The security provider has elevated its warning about a vulnerability affecting firewall management interfaces after observing active exploitation
dotnet9.0-9.0.100-1.fc40
Read Time:20 Second
FEDORA-2024-70cf80279f
Packages in this update:
dotnet9.0-9.0.100-1.fc40
Update description:
This is the .NET 9.0 GA release.
It contains security fixes for CVE-2024-43498 and CVE-2024-43499
Announcement: https://devblogs.microsoft.com/dotnet/announcing-dotnet-9/
Release Notes: https://github.com/dotnet/core/blob/main/release-notes/9.0/9.0.0/9.0.0.md
Bitfinex Hacker Jailed for Five Years Over Billion Dollar Crypto Heist
Read Time:5 Second
Ilya Lichtenstein hacked into the cryptocurrency exchange in 2016 and stole around 120,000 bitcoins
watchTowr Finds New Zero-Day Vulnerability in Fortinet Products
Read Time:6 Second
The new vulnerability was named “FortiJump Higher” due to its similarity with the “FortiJump” vulnerability discovered in October
Good Essay on the History of Bad Password Policies
Read Time:1 Minute, 23 Second
Stuart Schechter makes some good points on the history of bad password policies:
Morris and Thompson’s work brought much-needed data to highlight a problem that lots of people suspected was bad, but that had not been studied scientifically. Their work was a big step forward, if not for two mistakes that would impede future progress in improving passwords for decades.
First, was Morris and Thompson’s confidence that their solution, a password policy, would fix the underlying problem of weak passwords. They incorrectly assumed that if they prevented the specific categories of weakness that they had noted, that the result would be something strong. After implementing a requirement that password have multiple characters sets or more total characters, they wrote:
These improvements make it exceedingly difficult to find any individual password. The user is warned of the risks and if he cooperates, he is very safe indeed.
As should be obvious now, a user who chooses “p@ssword” to comply with policies such as those proposed by Morris and Thompson is not very safe indeed. Morris and Thompson assumed their intervention would be effective without testing its efficacy, considering its unintended consequences, or even defining a metric of success to test against. Not only did their hunch turn out to be wrong, but their second mistake prevented anyone from proving them wrong.
That second mistake was convincing sysadmins to hash passwords, so there was no way to evaluate how secure anyone’s password actually was. And it wasn’t until hackers started stealing and publishing large troves of actual passwords that we got the data: people are terrible at generating secure passwords, even with rules.
USN-7089-6: Linux kernel vulnerabilities
Read Time:4 Minute, 22 Second
Chenyuan Yang discovered that the USB Gadget subsystem in the Linux
kernel did not properly check for the device to be enabled before
writing. A local attacker could possibly use this to cause a denial of
service. (CVE-2024-25741)
Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
– ARM32 architecture;
– MIPS architecture;
– PA-RISC architecture;
– PowerPC architecture;
– RISC-V architecture;
– S390 architecture;
– x86 architecture;
– Cryptographic API;
– Serial ATA and Parallel ATA drivers;
– Null block device driver;
– Bluetooth drivers;
– Cdrom driver;
– Clock framework and drivers;
– Hardware crypto device drivers;
– CXL (Compute Express Link) drivers;
– Cirrus firmware drivers;
– GPIO subsystem;
– GPU drivers;
– I2C subsystem;
– IIO subsystem;
– InfiniBand drivers;
– ISDN/mISDN subsystem;
– LED subsystem;
– Multiple devices driver;
– Media drivers;
– Fastrpc Driver;
– Network drivers;
– Microsoft Azure Network Adapter (MANA) driver;
– Near Field Communication (NFC) drivers;
– NVME drivers;
– NVMEM (Non Volatile Memory) drivers;
– PCI subsystem;
– Pin controllers subsystem;
– x86 platform drivers;
– S/390 drivers;
– SCSI drivers;
– Thermal drivers;
– TTY drivers;
– UFS subsystem;
– USB DSL drivers;
– USB core drivers;
– DesignWare USB3 driver;
– USB Gadget drivers;
– USB Serial drivers;
– VFIO drivers;
– VHOST drivers;
– File systems infrastructure;
– BTRFS file system;
– GFS2 file system;
– JFFS2 file system;
– JFS file system;
– Network file systems library;
– Network file system client;
– NILFS2 file system;
– NTFS3 file system;
– SMB network file system;
– Memory management;
– Netfilter;
– Tracing infrastructure;
– io_uring subsystem;
– BPF subsystem;
– Core kernel;
– Bluetooth subsystem;
– CAN network layer;
– Ceph Core library;
– Networking core;
– IPv4 networking;
– IPv6 networking;
– IUCV driver;
– MAC80211 subsystem;
– Network traffic control;
– Sun RPC protocol;
– Wireless networking;
– AMD SoC Alsa drivers;
– SoC Audio for Freescale CPUs drivers;
– MediaTek ASoC drivers;
– SoC audio core drivers;
– SOF drivers;
– Sound sequencer drivers;
(CVE-2024-41062, CVE-2024-41029, CVE-2024-42142, CVE-2024-41070,
CVE-2024-41066, CVE-2024-42150, CVE-2024-42120, CVE-2023-52888,
CVE-2024-42141, CVE-2024-41032, CVE-2024-42245, CVE-2024-41053,
CVE-2024-42247, CVE-2024-42161, CVE-2024-42094, CVE-2024-41072,
CVE-2024-42076, CVE-2024-42091, CVE-2024-42103, CVE-2024-41007,
CVE-2024-42064, CVE-2024-41075, CVE-2024-42157, CVE-2024-42069,
CVE-2024-41045, CVE-2024-42068, CVE-2024-42090, CVE-2024-41071,
CVE-2024-42082, CVE-2024-42146, CVE-2024-41018, CVE-2024-42238,
CVE-2024-41079, CVE-2024-42241, CVE-2024-42067, CVE-2024-42132,
CVE-2024-42121, CVE-2024-41025, CVE-2024-42231, CVE-2024-42225,
CVE-2024-41080, CVE-2024-41086, CVE-2024-41012, CVE-2024-42234,
CVE-2024-41088, CVE-2024-42129, CVE-2024-42158, CVE-2024-41078,
CVE-2024-41038, CVE-2024-41055, CVE-2024-42106, CVE-2024-42227,
CVE-2024-42102, CVE-2024-41082, CVE-2024-42108, CVE-2024-41085,
CVE-2024-41020, CVE-2024-41054, CVE-2024-42085, CVE-2024-42140,
CVE-2024-42089, CVE-2024-41047, CVE-2024-42092, CVE-2024-41044,
CVE-2024-42246, CVE-2024-41035, CVE-2024-42250, CVE-2024-42070,
CVE-2024-41039, CVE-2024-41061, CVE-2024-42147, CVE-2024-42104,
CVE-2024-41090, CVE-2024-41096, CVE-2024-41063, CVE-2024-41084,
CVE-2024-41059, CVE-2024-41097, CVE-2024-41089, CVE-2024-42093,
CVE-2024-42126, CVE-2024-42135, CVE-2024-42128, CVE-2024-42098,
CVE-2024-42105, CVE-2024-42124, CVE-2024-42101, CVE-2024-41091,
CVE-2024-42127, CVE-2024-41077, CVE-2024-42111, CVE-2024-41037,
CVE-2024-42136, CVE-2024-41083, CVE-2024-42243, CVE-2024-41033,
CVE-2024-41046, CVE-2024-42230, CVE-2024-42080, CVE-2024-42096,
CVE-2024-42100, CVE-2024-42236, CVE-2024-41022, CVE-2024-42086,
CVE-2024-42251, CVE-2024-41015, CVE-2024-41027, CVE-2024-42155,
CVE-2024-42117, CVE-2024-41036, CVE-2024-42133, CVE-2024-41010,
CVE-2024-42151, CVE-2024-42118, CVE-2024-39486, CVE-2024-42066,
CVE-2024-42131, CVE-2024-42223, CVE-2024-41081, CVE-2024-42244,
CVE-2024-41073, CVE-2024-42114, CVE-2024-42252, CVE-2024-42248,
CVE-2024-42110, CVE-2024-41051, CVE-2023-52887, CVE-2024-42156,
CVE-2024-41074, CVE-2024-41017, CVE-2024-42079, CVE-2024-41034,
CVE-2024-41028, CVE-2024-42109, CVE-2024-42235, CVE-2024-41058,
CVE-2024-42232, CVE-2024-42084, CVE-2024-41076, CVE-2024-41030,
CVE-2024-41023, CVE-2024-42271, CVE-2024-41050, CVE-2024-41042,
CVE-2024-41031, CVE-2024-42112, CVE-2024-41092, CVE-2024-42253,
CVE-2024-42152, CVE-2024-41049, CVE-2024-42237, CVE-2024-41095,
CVE-2024-42280, CVE-2024-42153, CVE-2024-42115, CVE-2024-42130,
CVE-2024-41064, CVE-2024-42077, CVE-2024-41067, CVE-2024-42137,
CVE-2024-41019, CVE-2024-42240, CVE-2024-41093, CVE-2024-41048,
CVE-2024-42063, CVE-2024-42113, CVE-2024-42145, CVE-2024-42073,
CVE-2024-43858, CVE-2024-42088, CVE-2024-41069, CVE-2024-41068,
CVE-2024-42138, CVE-2024-41065, CVE-2024-42087, CVE-2024-42239,
CVE-2024-42149, CVE-2024-41021, CVE-2024-42065, CVE-2024-39487,
CVE-2024-41052, CVE-2024-42095, CVE-2024-42074, CVE-2024-42097,
CVE-2024-41098, CVE-2024-41057, CVE-2024-41060, CVE-2024-42119,
CVE-2024-42229, CVE-2024-43855, CVE-2024-41056, CVE-2024-41041,
CVE-2024-42144, CVE-2024-41087, CVE-2024-41094)