Monthly Archives: July 2024

Advisories

python-zipp-3.16.2-3.fc39

Read Time:7 Second

FEDORA-2024-f69e3c5255

Packages in this update:

python-zipp-3.16.2-3.fc39

Update description:

Security fix for CVE-2024-5569 (rhbz#2297117)

Read More

Advisories

tcpreplay-4.5.1-1.el8

Read Time:2 Minute, 52 Second

FEDORA-EPEL-2024-b9b7864353

Packages in this update:

tcpreplay-4.5.1-1.el8

Update description:

Announcing v4.5.1

This release contains contributions from a record number of new contributors. This is greatly appreciated since I am a team of one, and do Tcpreplay maintenance in my spare time.

There are many bug fixes and new features. Most notable features:

AF_XDP socket support – if you have a newer Linux kernel, you will be able to transmit at line rates without having to install 3rd party kernel modules (e.g. netmap, PF_RING)
-w tcpreplay option – this overrides the -i option, and allows you to write to a PCAP file rather than an interface
–include and –exclude tcpreplay options – allows replay of a list of specific packet numbers to replay. This may slow things down, so consider using in combination with -w.
–fixhdrlen tcpreplay option – added to control action on packet length changes
-W tcpreplay option – suppress warnings when replaying
SLL2( Linux “cooked” capture encapsulation v2)
Haiku support

What’s Changed

Add support for LINUX_SLL2 by @btriller in #728
Feature #727 – Linux SLL v2 by @fklassen in #820
Bug #779 – honour overflow for all PPS values by @fklassen in #821
AF_XDP socket extension using libxdp api by @plangarbalint in #797
Feature #822 – AF_XDP socket extension by @fklassen in #823
Nanosec accurate packet processing by @plangarbalint in #796
Handle IPv6 fragment extension header by @ChuckCottrill in #832
Bug #837 – handle IPv6 fragment extension header by @fklassen in #838
Feature #796 – nanosecond packet processing by @fklassen in #836
configure.ac: unify search dirs for pcap and add lib32 by @shr-project in #819
Feature #839 – add pull request template by @fklassen in #840
ipv6 – add check for extension header length by @GabrielGanne in #842
Bug #827 PR #842 IPv6 extension header – staging by @fklassen in #859
add check for empty cidr by @GabrielGanne in #843
Bug #824 and PR #843: check for empty CIDR by @fklassen in #860
Add option to turn on/off fix packet header length by @ChuckCottrill in #846
Bug #703 #844 PR #846: optionally fix packet header length –fixhdrlen by @fklassen in #861
Bug 863: fix nansecond timestamp regression by @fklassen in #865
autotools – AC_HELP_STRING is obsolete in 2.70 by @GabrielGanne in #856
some Haiku support by @infrastation in #847
configure.ac: do not run conftest in case of cross compilation by @ChenQi1989 in #849
dlt_jnpr_ether_cleanup: check config before cleanup by @Marsman1996 in #851
Fix recursive tcpedit cleanup by @GabrielGanne in #855
Bug #813: back out PR #855 by @fklassen in #866
Bug #867 – run regfree() on close by @fklassen in #868
Bug #869 tcpprep memory leak include exclude by @fklassen in #870
Bug #811 – add check for invalid jnpr header length by @fklassen in #872
Bug #792 avoid assertion and other fixes by @fklassen in #873
Bug #844 tap: ignore TUNSETIFF EBUSY errors by @fklassen in #874
Bug #876 – add missing free_umem_and_xsk function by @fklassen in #877
Feature #878 – add -w / –suppress-warning option by @fklassen in #879
Bug #835 false unsupported dlt warnings on 802.3 (Ethernet I) and LLC by @fklassen in #880
Feature #884 include exclude options by @fklassen in #885
Feature #853 direct traffic to pcap by @fklassen in #871
Feature #853 restore missing -P command by @fklassen in #887
Bug #888: check for map == NULL in cidr.c by @fklassen in #889

Read More

News

Hacking Scientific Citations

Read Time:1 Minute, 23 Second

Some scholars are inflating their reference counts by sneaking them into metadata:

Citations of scientific work abide by a standardized referencing system: Each reference explicitly mentions at least the title, authors’ names, publication year, journal or conference name, and page numbers of the cited publication. These details are stored as metadata, not visible in the article’s text directly, but assigned to a digital object identifier, or DOI—a unique identifier for each scientific publication.

References in a scientific publication allow authors to justify methodological choices or present the results of past studies, highlighting the iterative and collaborative nature of science.

However, we found through a chance encounter that some unscrupulous actors have added extra references, invisible in the text but present in the articles’ metadata, when they submitted the articles to scientific databases. The result? Citation counts for certain researchers or journals have skyrocketed, even though these references were not cited by the authors in their articles.

[…]

In the journals published by Technoscience Academy, at least 9% of recorded references were “sneaked references.” These additional references were only in the metadata, distorting citation counts and giving certain authors an unfair advantage. Some legitimate references were also lost, meaning they were not present in the metadata.

In addition, when analyzing the sneaked references, we found that they highly benefited some researchers. For example, a single researcher who was associated with Technoscience Academy benefited from more than 3,000 additional illegitimate citations. Some journals from the same publisher benefited from a couple hundred additional sneaked citations.

Be careful what you’re measuring, because that’s what you’ll get. Make sure it’s what you actually want.

Read More

News

Disney hacked? NullBulge claims to have stolen 1.1 TB of data from internal Slack channels

Read Time:24 Second

A group of hacktivists claims to have breached the IT systems of Disney, and stolen a gigantic 1.1 terabytes worth of data from the entertainment giant’s internal Slack messaging channels.

The hacking group, which calls itself NullBulge, posted on an underground hacking forum that it had hoped to postpone announcing the breach until it had accessed more information, “but our insider man got cold feet and kicked us out.”

Read more in my article on the Hot for Security blog.

Read More

Advisories

USN-6898-1: Linux kernel vulnerabilities

Read Time:4 Minute, 18 Second

Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not
properly handle certain error conditions, leading to a NULL pointer
dereference. A local attacker could possibly trigger this vulnerability to
cause a denial of service. (CVE-2022-38096)

Gui-Dong Han discovered that the software RAID driver in the Linux kernel
contained a race condition, leading to an integer overflow vulnerability. A
privileged attacker could possibly use this to cause a denial of service
(system crash). (CVE-2024-23307)

It was discovered that a race condition existed in the Bluetooth subsystem
in the Linux kernel when modifying certain settings values through debugfs.
A privileged local attacker could use this to cause a denial of service.
(CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in
the Linux kernel contained a race condition, leading to an integer overflow
vulnerability. An attacker could possibly use this to cause a denial of
service (system crash). (CVE-2024-24861)

Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device
volume management subsystem did not properly validate logical eraseblock
sizes in certain situations. An attacker could possibly use this to cause a
denial of service (system crash). (CVE-2024-25739)

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:
– ARM64 architecture;
– RISC-V architecture;
– x86 architecture;
– Block layer subsystem;
– Accessibility subsystem;
– Android drivers;
– Bluetooth drivers;
– Clock framework and drivers;
– Data acquisition framework and drivers;
– Cryptographic API;
– DMA engine subsystem;
– GPU drivers;
– HID subsystem;
– I2C subsystem;
– IRQ chip drivers;
– Multiple devices driver;
– VMware VMCI Driver;
– MMC subsystem;
– Network drivers;
– Microsoft Azure Network Adapter (MANA) driver;
– Device tree and open firmware driver;
– PCI subsystem;
– S/390 drivers;
– SCSI drivers;
– Freescale SoC drivers;
– Trusted Execution Environment drivers;
– TTY drivers;
– USB subsystem;
– VFIO drivers;
– Framebuffer layer;
– Xen hypervisor drivers;
– File systems infrastructure;
– BTRFS file system;
– Ext4 file system;
– FAT file system;
– Network file system client;
– Network file system server daemon;
– NILFS2 file system;
– Pstore file system;
– SMB network file system;
– UBI file system;
– Netfilter;
– BPF subsystem;
– Core kernel;
– PCI iomap interfaces;
– Memory management;
– B.A.T.M.A.N. meshing protocol;
– Bluetooth subsystem;
– Ethernet bridge;
– Networking core;
– IPv4 networking;
– IPv6 networking;
– MAC80211 subsystem;
– IEEE 802.15.4 subsystem;
– NFC subsystem;
– Open vSwitch;
– RDS protocol;
– Network traffic control;
– SMC sockets;
– Unix domain sockets;
– eXpress Data Path;
– Key management;
– ALSA SH drivers;
– KVM core;
(CVE-2024-35944, CVE-2024-35789, CVE-2024-35819, CVE-2024-35796,
CVE-2024-35817, CVE-2024-35950, CVE-2024-35851, CVE-2024-35918,
CVE-2024-26961, CVE-2024-35990, CVE-2024-26629, CVE-2024-35823,
CVE-2024-35922, CVE-2024-26969, CVE-2024-36007, CVE-2024-35989,
CVE-2024-35822, CVE-2024-26654, CVE-2024-35879, CVE-2024-27395,
CVE-2024-35855, CVE-2024-27008, CVE-2024-26988, CVE-2024-35912,
CVE-2024-35900, CVE-2024-26956, CVE-2024-27018, CVE-2024-26922,
CVE-2024-26950, CVE-2024-35849, CVE-2024-26999, CVE-2024-36006,
CVE-2024-26970, CVE-2024-26937, CVE-2024-35821, CVE-2024-35982,
CVE-2024-35907, CVE-2024-35884, CVE-2024-26929, CVE-2024-35905,
CVE-2024-35915, CVE-2024-35910, CVE-2024-35886, CVE-2024-35930,
CVE-2024-36008, CVE-2024-27004, CVE-2024-26984, CVE-2024-35877,
CVE-2024-35958, CVE-2024-35895, CVE-2024-26981, CVE-2024-27393,
CVE-2024-35973, CVE-2024-36029, CVE-2024-26931, CVE-2024-35934,
CVE-2024-35902, CVE-2024-27013, CVE-2024-26951, CVE-2024-35901,
CVE-2024-35938, CVE-2024-35936, CVE-2024-26958, CVE-2024-27059,
CVE-2024-27001, CVE-2024-35825, CVE-2024-35925, CVE-2024-36004,
CVE-2024-26960, CVE-2024-26923, CVE-2024-35927, CVE-2024-27009,
CVE-2024-35847, CVE-2024-35871, CVE-2024-27020, CVE-2024-26811,
CVE-2024-35897, CVE-2024-26994, CVE-2024-35935, CVE-2024-35978,
CVE-2024-26934, CVE-2024-26828, CVE-2023-52699, CVE-2024-26810,
CVE-2024-35890, CVE-2024-35955, CVE-2024-35899, CVE-2024-35885,
CVE-2024-36020, CVE-2024-26813, CVE-2024-26814, CVE-2024-27016,
CVE-2024-35852, CVE-2024-27437, CVE-2024-35933, CVE-2024-35857,
CVE-2024-26973, CVE-2024-35813, CVE-2024-27015, CVE-2024-35791,
CVE-2024-26687, CVE-2024-35976, CVE-2024-35853, CVE-2024-35969,
CVE-2024-35940, CVE-2024-35809, CVE-2024-35888, CVE-2023-52488,
CVE-2024-26926, CVE-2024-36005, CVE-2024-26996, CVE-2024-27000,
CVE-2024-26957, CVE-2024-26974, CVE-2024-26977, CVE-2024-36031,
CVE-2024-26966, CVE-2024-35815, CVE-2024-35960, CVE-2024-35806,
CVE-2024-26642, CVE-2023-52880, CVE-2024-26925, CVE-2024-26989,
CVE-2024-26965, CVE-2024-35997, CVE-2024-26993, CVE-2024-26955,
CVE-2024-35872, CVE-2024-35893, CVE-2024-35896, CVE-2024-35805,
CVE-2024-27019, CVE-2024-35898, CVE-2024-35970, CVE-2024-35988,
CVE-2024-35854, CVE-2024-26976, CVE-2024-35984, CVE-2024-35804,
CVE-2024-35807, CVE-2024-26964, CVE-2024-36025, CVE-2024-27396,
CVE-2024-26935, CVE-2024-35785, CVE-2024-26812, CVE-2024-26817)

Read More