| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| A legacy code path allowed users to craft requests to a ticket shop that bypass some validation steps for the selected products. In consequence, this could lead to an attacker purchasing products that are in fact sold out. |
| Our payment integration with Stripe did not properly validate payment status responses. An attacker could use a successful payment status response from one payment and supply it to the system for a different payment, gaining access to multiple valid tickets with only one payment. However, the attack requires knowledge of a valid charge ID from the same event which we believe is usually not exposed to users.
To simplify attack surface, the fix removes support for incoming webhooks regarding payments created through Stripe's old "source" API. pretix stopped creating payments using this API in 2024.1 for most payment methods and in 2024.9 for all payment methods. |
| When configuring a device to use the security profile "pretixSCAN (kiosk mode, no order sync, no search)", the API search endpoint introduced in pretix 4.12 was not blocked correctly. This theoretically allows these devices to perform searches for orders even if that was not intended. If the device is in kiosk mode, the search button will still be hidden from users. |
| pretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to. |
| Missing Authorization vulnerability in PublishPress PublishPress Permissions press-permit-core allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PublishPress Permissions: from n/a through 5.0.1. |
| Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may
cause OpenSSL to allocate a full message-length reassembly buffer for each
buffered message, so a small amount of wire data consumes a large amount of
memory.
Impact summary: A remote attacker can send a few small crafted DTLS handshake
fragments to make a DTLS server or client allocate well over a megabyte of
memory per connection, which may lead to memory exhaustion and Denial of
Service if many connections are made.
CWE: CWE-770: Allocation of Resources Without Limits or Throttling
Description: DTLS handshake messages can arrive out of order and fragmented,
so OpenSSL buffers fragments of up to ten out-of-sequence messages until
reassembly is possible. When the first fragment of a new message arrives,
OpenSSL allocates a buffer sized to the full message length declared in the
fragment header, plus a reassembly bitmap, instead of storing only the bytes
actually received. The declared length is capped by the maximum certificate
list size, 128KB by default, and that cap applies to every handshake message
type rather than only to Certificate messages.
Only DTLS endpoints reach this code. TLS, QUIC and applications that do not
use DTLS are unaffected. An attacker sends fragments that declare a large
message length but carry almost no data, using up to ten distinct message
sequence numbers.
A single connection can then hold roughly 1.4MB of buffers from about 156
bytes on the wire. Because the number of buffered messages is capped, memory
exhaustion requires many connections or many peers, which is why the severity
is Low.
FIPS impact: no
The affected code is outside the FIPS module boundary. |
| Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL
pointer when processing an unusual combination of certificate and TLSA
records.
Impact summary: The impact is limited to a client crash (potential Denial
of Service).
CWE: CWE-476: NULL Pointer Dereference
Description: A DANE-enabled TLS client that supports TLSA records with at
least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2)
usage may crash by dereferencing a NULL pointer if the server claims a trusted
CA's certificate to be its end-entity certificate and has an unusual mix of
associated TLSA records.
DANE SMTP clients should not be affected since only the
DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable
in SMTP. For example, the Postfix MTA is not affected, while the Exim
MTA does not at present use OpenSSL's DANE implementation.
Use of DANE in validation of RFC7250 raw public keys (RPKs) is also
unaffected, as these only use DANE-EE(3) TLSA records.
Only applications that support combining the DANE PKI with a traditional PKI
are potentially affected. A DANE-enabled browser or similar, that uses
OpenSSL's DANE API could be affected.
FIPS impact: no
The DANE API is outside the FIPS module boundary. |
| Authenticated users can bypass normal controls on the reading and writing of workflow execution results. This allows any authenticated user to read or modify any other user's workflow execution results.
This issue affects Apache Texera (incubating): from 1.1.0-incubating before 1.3.0-incubating.
Users are recommended to upgrade to version 1.3.0-incubating, which fixes the issue. |
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Liquid Web / StellarWP Gutenberg Blocks by Kadence Blocks kadence-blocks allows Stored XSS.This issue affects Gutenberg Blocks by Kadence Blocks: from n/a through 3.9.1.1. |
| Missing Authorization vulnerability in Magepeople inc. Taxi Booking Manager for WooCommerce ecab-taxi-booking-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Taxi Booking Manager for WooCommerce: from n/a through 2.2.10. |
| Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Brainstorm Force Spectra ultimate-addons-for-gutenberg allows Stored XSS.This issue affects Spectra: from n/a through 2.20.6. |
| Missing Authorization vulnerability in myCred myCred mycred allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects myCred: from n/a through 4.0.3. |
| A malicious actor with access to the network and low privileges could exploit an Improper Link Resolution Before File Access vulnerability found in UniFi Access Application to execute arbitrary code with root privileges on the host device. |
| A malicious actor with access to the network and low privileges could exploit a series of authenticated SQL Injection vulnerabilities found in UniFi Access Application to escalate privileges on the host device. |
| A malicious actor with access to the network and low privileges could exploit a Server-Side Request Forgery (SSRF) vulnerability found in UniFi Access Application to escalate privileges within UniFi OS. |
| A malicious actor with access to the network and low privileges could exploit an authenticated SQL Injection vulnerability found in UniFi Access Application to obtain sensitive information and make unauthorized changes within the UniFi Access Application. |
| A malicious actor with access to the network and under certain conditions could exploit an Improper Certificate Validation vulnerability found in UniFi Access Application to obtain sensitive information from and make unauthorized changes to an adopted UniFi Access device. |
| A malicious actor with access to the network and low privileges could exploit an Incorrect Authorization vulnerability found in UniFi Access Application to execute arbitrary commands on certain adopted UniFi Access devices. |
| The SAML SSO Login WordPress plugin through 1.5.2 does not verify that the SAML assertion whose signature it validates is the same assertion it reads the user identity from, allowing unauthenticated attackers who hold a validly signed assertion for any identity to authenticate as any existing user, including an administrator, through XML signature wrapping. |
| The AppPresser WordPress plugin before 5.0.0 does not properly escape the contents of its debug log when displaying it in the admin dashboard, and decodes escape sequences after sanitising input, allowing unauthenticated users to perform Stored XSS attacks against administrators when debug logging is enabled. |