| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Issue summary: A QUIC server that rejects a stream opened by the peer may
retain that stream's state for the lifetime of the connection if the peer
resets the stream before the rejection is signalled, even though the peer's
stream credit is returned.
Impact summary: A remote client that completes a QUIC handshake can repeatedly
open and reset streams, causing server memory to grow without bound until the
process runs out of memory and every connection on it is lost. This is a
Denial of Service.
CWE: CWE-401: Missing Release of Memory after Effective Lifetime
Description: QUIC servers track each stream the peer opens. When the incoming
stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks
the stream deleted and returns the peer's stream credit. A deleted stream is
collected only once its receive part is fully drained, which for a rejected
stream means the STOP_SENDING has been acknowledged. If the peer sends
RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never
sent or acknowledged and the stream is never collected.
The default configuration reaches this path. Once a connection has a default
stream, meaning the application has read from or written to the connection as
the tutorial server does, the effective incoming stream policy rejects streams
the application does not accept. Applications that set the REJECT policy
explicitly are affected too.
Each retained stream costs about 300 bytes, and the peer's stream credit
window paces how quickly they accumulate. A client that keeps the connection
open and keeps opening and resetting streams grows server memory without
bound. The severity is Low because growth is slow, needs a long-lived
connection, and causes no memory corruption or disclosure.
FIPS impact: no
The affected code is outside the FIPS module boundary. |
| Issue summary: A server configured with the Suite B certificate flag through
SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a
fixed group list when it processes a ClientHello whose supported_groups and
key_share contain no Suite B group.
Impact summary: A remote client can send a ClientHello that makes the server
read past the end of a static array. The values read are never returned to the
client, so no memory is disclosed; on builds with sanitizers or hardened
allocators the read may crash the process, causing Denial of Service.
CWE: CWE-125: Out-of-bounds Read
Description: When the Suite B certificate flag is set, OpenSSL restricts the
accepted groups to P-256 and P-384 by substituting a fixed two-element list
for the configured group list. The tuple machinery used for key-share
selection was not updated for this substitution: tls1_get_group_tuples() still
returns the configured tuples, which by default describe eight groups. The
server-side walk in tls_parse_ctos_key_share() then advances through the
two-element list using those tuple counts without checking the cumulative
offset against the number of groups present.
Only applications that call SSL_CTX_set_cert_flags() with
SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The
openssl s_server -suiteB_128 option sets an X.509 verification parameter
instead, so the stock command line server is not vulnerable. Default
configurations do not reach this code.
A client that offers only groups outside the Suite B set, such as X25519,
forces every tuple to be walked and the read to run past the array. The bytes
read are compared against client group IDs and never sent back, so no memory
is disclosed. On builds with address sanitizers or hardened allocators the
read can abort the process; in ordinary release builds it reads a few bytes of
adjacent constant data.
FIPS impact: no
The affected code is outside the FIPS module boundary. |
| The CODESYS Automation Server Connector uses server-supplied file names without sufficient path traversal checks. An unauthenticated remote attacker controlling a malicious Automation Server and tricking a user to trust it, or performing a man-in-the-middle attack on a trusted communication channel, can exploit this vulnerability to write attacker-controlled files to arbitrary locations on the engineering workstation and subsequently achieve arbitrary code execution with user privileges. |
| The affected products do not sufficiently validate CODESYS Automation Server TLS certificates when a user starts the certificate enrollment. An unauthenticated remote attacker performing a man-in-the-middle attack can exploit this vulnerability by supplying an untrusted certificate that is accepted as trusted. Successful exploitation may allow an attacker to intercept and manipulate communications between the CODESYS Automation Server and the PLC network. |
| The affected products process a server-supplied URL without sufficient validation. An unauthenticated remote attacker controlling a malicious Automation Server and tricking a user to trust it or performing a man-in-the-middle attack, can exploit this vulnerability by causing the affected product to process unintended content. Successful exploitation may result in arbitrary code execution with the privileges of the user running the affected product. |
| A Cross-Site Scripting (XSS) vulnerability reflected in the GET parameters `cod_primaria` and `cod_secundaria` of the Novanet Web endpoints `NNws_ShwNewDup` and `NPcd/NFG_VerNoticia`. User-provided data is reflected within a JavaScript block without proper sanitization or context-appropriate output encoding. An unauthenticated remote attacker could craft a manipulated URL that, when visited by a victim, would execute arbitrary JavaScript code in the victim’s browser, within the context of the affected site. The flaw resides in the platform’s shared code, so it could affect organizations using that vulnerable code. |
| In Eclipse Theia versions 1.66.0 and up until including 1.73.1, the `@theia/plugin-ext` backend exposes the `/hostedPlugin/:pluginId/:path(*)` HTTP endpoint, which resolves the requested file path with `path.resolve(localPath, filePath)` without verifying that the resolved path stays within the plugin's directory. An unauthenticated network attacker can send percent-encoded `../` sequences (`%2e%2e%2f`) that decode into the path parameter and escape the plugin directory, allowing arbitrary files readable by the Theia backend process to be retrieved. Plugin IDs are derived deterministically from a plugin's publisher and name, so built-in plugins serve as reliable anchors that require no prior knowledge of the target system. |
| In the Matter door lock applications of
the Nordic Semiconductor nRF Door Lock and Access Control Add-on v1.0.0
through v1.1.1, AccessManager::ValidateCredential() checks only credential
occupancy and the secret bytes, and never reads the owning user's UserStatus.
It also returns success when no owning user can be resolved. A user suspended
by setting their status to OccupiedDisabled can continue to unlock the door
with their previously assigned credential, and an orphaned but occupied
credential is also accepted. Fixed in v1.2.0. |
| In
the Matter and Aliro Door Lock Application of the Nordic Semiconductor nRF Door
Lock and Access Control Add-on v1.0.0 through v1.1.1 with
CONFIG_DOOR_LOCK_STEP_UP_PHASE enabled, deleting a Credential Issuer passes the
1-based Matter credential index to ClearValidityIterations(), which expects a
0-based storage index. The intended issuer's ValidityIteration state is left in
place, and the state of the adjacent, still-provisioned issuer is cleared. This
resets that issuer's rollback protection. An attacker holding an older but correctly
signed Access Document from the adjacent issuer, whose validity iteration had
been superseded, can then potentially obtain physical access. Fixed in v1.2.0. |
| In the Aliro access control reference
applications of the Nordic Semiconductor nRF Door Lock and Access Control
Add-on v1.0.0 through v1.1.1, the stored Access Document record does not
retain validFrom and validUntil. The cached public key path (VerifyPublicKey())
and the Kpersistent fast path (_VerifyKPersistentKey()) therefore never
re-evaluate the Access Document validity period. An attacker who held a
time-limited Aliro credential that was valid when first presented can
continue to obtain physical access after the Access Document has expired, for
as long as the cached record remains available. Fixed in v1.2.0. |
| In the Aliro access control reference
applications of the Nordic Semiconductor nRF Door Lock and Access Control
Add-on v1.0.0 through v1.1.1, built with Credential Issuer CA
certificate-based issuer trust (CONFIG_DOOR_LOCK_CREDENTIAL_ISSUER_CA) and
the Aliro Step-up phase (CONFIG_DOOR_LOCK_STEP_UP_PHASE) enabled,
AccessManagerImpl::ProcessValidityIteration() treats a failed lookup of the
Credential Issuer in the provisioned issuer array as success. For an issuer
trusted through a certificate chain but not provisioned, the
ValidityIteration (credential-rollback) check is therefore skipped. A former
authorized holder with an old but correctly issuer-signed Access Document can
be granted physical access after the issuer has advanced its iteration to
revoke that credential. The default Matter provisioning configuration is not
affected. Fixed in v1.2.0. |
| Hidden functionality issue exists in WRC-BE36QS-B , WRC-W701-B, and WRC-BE94XS-B. If exploited, the product's hidden debug function may be enabled by a remote attacker who can log in to WebGUI. |
| WRC-BE36QS-B, WRC-W701-B, and WRC-BE94XS-B contain an improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability in WebGUI. If exploited, an arbitrary OS command may be executed by a remote attacker who can log in to WebGUI. |
| The Soledad theme for WordPress is vulnerable to unauthenticated Remote Code Execution in versions up to, and including, 8.7.7 The public penci_more_post_ajax AJAX action feeds infeedads[ads_code] (base64+urldecoded) to penci_safe_shortcode(), whose allowlist regex inspects only the hyphen-truncated outer shortcode name (e.g. 'adinserter') and never the nested [elementor-element k=.. data=..] tag, so do_shortcode() renders an attacker-chosen Elementor element. The rendered penci-featured-sliders widget passes its unsanitized 'style' setting to include dirname(__FILE__)."/{$style}.php", a path-traversal local file inclusion. |
| Joomla Extension - php-web-design.com - CSRF for various actions in StageIt 1.0.0-2.2.0, 3.0.0-4.2.0, 5.0.0-5.7.5, 6.0.0-6.3.5 |
| Joomla Extension - php-web-design.com - RCE via setting strings in StageIt 1.0.0-2.2.0, 3.0.0-4.2.0, 5.0.0-5.7.5, 6.0.0-6.3.5 |
| Joomla Extension - php-web-design.com - Reflected XSS in StageIt 1.0.0-2.2.0, 3.0.0-4.2.0, 5.0.0-5.7.5, 6.0.0-6.3.5 |
| The All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 5.0.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that an administrator has placed the AIOSEO breadcrumb on the author template, that the site is running WordPress 6.6 or later with the core Interactivity runtime loaded (e.g., via a block theme or core/navigation block), and that a victim clicks the rendered breadcrumb link on the author archive page. |
| Joomla Extension - valorapps.com - Unauthenticated Remote Code Execution in Easy File Uploader < 2.9.7 - An unauthenticated remote attacker can upload a PHP-executable file to the Joomla web root with a single multipart POST request, requiring no credentials and no CSRF token. |
| A improper neutralization of special elements used in an os command ('os command injection') vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.4, FortiMail 7.4.0 through 7.4.6, FortiMail 7.2 all versions, FortiRecorder 7.6.0 through 7.6.2, FortiRecorder 7.2.0 through 7.2.12, FortiRecorder 7.0.0 through 7.0.6 may allow an authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP requests. |