4414 matches found
Race Condition within a Thread
Overview outray is an OutRay CLI - Expose your local server to the internet Affected versions of this package are vulnerable to Race Condition within a Thread due to the lack of transaction locking mechanisms in main/apps/web/src/routes/api/$orgSlug/subdomains/index.ts. An attacker can obtain mor...
Outray 安全漏洞
Outray is a local server building tool from OutRay open source. A security vulnerability exists in Outray versions prior to 0.1.5, which stems from a missing database transaction locking mechanism that could lead to free plan users acquiring more subdomains than expected...
Unity Linux 20.1070e Security Update: kernel (UTSA-2026-001680)
The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-001680 advisory. st21nfcaconnectivityeventreceived in drivers/nfc/st21nfca/se.c in the Linux kernel through 5.16.12 has EVTTRANSACTION buffer overflows because of untrusted length...
GHSA-45HJ-9X76-WP9G Outray has a Race Condition in the cli's webapp
Summary This vulnerability allows a user i.e a free plan user to get more than the desired subdomains due to lack of db transaction lock mechanisms in https://github.com/akinloluwami/outray/blob/main/apps/web/src/routes/api/%24orgSlug/subdomains/index.ts Details - The affected code-: ts //Race...
Outray has a Race Condition in the cli's webapp
Summary This vulnerability allows a user i.e a free plan user to get more than the desired subdomains due to lack of db transaction lock mechanisms in https://github.com/akinloluwami/outray/blob/main/apps/web/src/routes/api/%24orgSlug/subdomains/index.ts Details - The affected code-: ts //Race...
AZL-74348 CVE-2025-68778 affecting package kernel for versions less than 6.6.121.1-1
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current...
CVE-2025-68778
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current...
UBUNTU-CVE-2025-68778
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current...
CVE-2025-68778
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current...
CVE-2025-68778 btrfs: don't log conflicting inode if it's a dir moved in the current transaction
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current...
CVE-2025-68778
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current...
CVE-2025-68778
CVE-2025-68778 corresponds to a Linux kernel Btrfs logging/transaction bug where logging an inode location while moving a directory in the same transaction could cause an inconsistent log replay, potentially leading to a hard-link count issue and a failed mount. The provided advisories confirm th...
CVE-2025-68778 btrfs: don't log conflicting inode if it's a dir moved in the current transaction
In the Linux kernel, the following vulnerability has been resolved: btrfs: don't log conflicting inode if it's a dir moved in the current transaction We can't log a conflicting inode if it's a directory and it was moved from one parent directory to another parent directory in the current...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in the Linux kernel that stems from logging conflicting inodes when moving a directory in the current transaction, which could result in two har...
PT-2026-2971
Summary This vulnerability allows a user i.e a free plan user to get more than the desired subdomains due to lack of db transaction lock mechanisms in https://github.com/akinloluwami/outray/blob/main/apps/web/src/routes/api/%24orgSlug/subdomains/index.ts Details - The affected code-: ts //Race...
CVE-2023-50311
IBM CICS Transaction Gateway for Multiplatforms 9.2 and 9.3 could disclose sensitive path information to an attacker that could reveal through debugging or error messages...
CVE-2023-49958
An issue was discovered in Dalmann OCPP.Core through 1.2.0 for OCPP Open Charge Point Protocol for electric vehicles. The server processes mishandle StartTransaction messages containing additional, arbitrary properties, or duplicate properties. The last occurrence of a duplicate property is...
CVE-2023-31442
In Lightbend Akka before 2.8.1, the async-dns resolver used by Discovery in DNS mode and transitively by Cluster Bootstrap uses predictable DNS transaction IDs when resolving DNS records, making DNS resolution subject to poisoning by an attacker. If the application performing discovery does not...
CVE-2010-0362
Zeus Web Server before 4.3r5 does not use random transaction IDs for DNS requests, which makes it easier for remote attackers to spoof DNS responses...
CVE-2022-33988
dproxy-nexgen aka dproxy nexgen re-uses the DNS transaction id TXID value from client queries, which allows attackers able to send queries to the resolver to conduct DNS cache-poisoning attacks because the TXID value is known to the attacker...