CWE-287
DiscouragedImproper Authentication
Abstraction: Class · Status: Draft
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
5960 vulnerabilities reference this CWE, most recent first.
GHSA-XX6M-M9V2-VC78
Vulnerability from github – Published: 2022-05-24 17:42 – Updated: 2022-10-24 19:00Attackers can access the CGE account management function without privilege for permission elevation and execute arbitrary commands or files after obtaining user permissions.
{
"affected": [],
"aliases": [
"CVE-2021-22858"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-434"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-02-17T11:15:00Z",
"severity": "HIGH"
},
"details": "Attackers can access the CGE account management function without privilege for permission elevation and execute arbitrary commands or files after obtaining user permissions.",
"id": "GHSA-xx6m-m9v2-vc78",
"modified": "2022-10-24T19:00:18Z",
"published": "2022-05-24T17:42:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-22858"
},
{
"type": "WEB",
"url": "https://www.chtsecurity.com/news/fe1e30ef-4dac-4848-a3c9-a7df12672422"
},
{
"type": "WEB",
"url": "https://www.twcert.org.tw/tw/cp-132-4396-e6d44-1.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-XX73-XG4M-9C9J
Vulnerability from github – Published: 2022-05-24 17:19 – Updated: 2022-05-24 17:19An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. The DeX Lockscreen feature does not block access to Quick Panel and notifications. The Samsung ID is SVE-2020-17187 (June 2020).
{
"affected": [],
"aliases": [
"CVE-2020-13838"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-06-04T18:15:00Z",
"severity": "LOW"
},
"details": "An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. The DeX Lockscreen feature does not block access to Quick Panel and notifications. The Samsung ID is SVE-2020-17187 (June 2020).",
"id": "GHSA-xx73-xg4m-9c9j",
"modified": "2022-05-24T17:19:21Z",
"published": "2022-05-24T17:19:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-13838"
},
{
"type": "WEB",
"url": "https://security.samsungmobile.com/securityUpdate.smsb"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-XXC2-J7JJ-6G5M
Vulnerability from github – Published: 2022-08-05 00:00 – Updated: 2022-08-11 21:14An issue in Renato v0.17.0 allows attackers to cause a Denial of Service (DoS) via a crafted payload injected into the Search parameter.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.17.0"
},
"package": {
"ecosystem": "npm",
"name": "raneto"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.17.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2022-35142"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2022-08-11T21:14:43Z",
"nvd_published_at": "2022-08-04T20:15:00Z",
"severity": "HIGH"
},
"details": "An issue in Renato v0.17.0 allows attackers to cause a Denial of Service (DoS) via a crafted payload injected into the `Search` parameter.",
"id": "GHSA-xxc2-j7jj-6g5m",
"modified": "2022-08-11T21:14:43Z",
"published": "2022-08-05T00:00:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-35142"
},
{
"type": "WEB",
"url": "https://github.com/ryanlelek/Raneto/issues/368"
},
{
"type": "WEB",
"url": "https://github.com/ryanlelek/Raneto/pull/370"
},
{
"type": "WEB",
"url": "https://cwe.mitre.org/data/definitions/703.html"
},
{
"type": "WEB",
"url": "https://gainsec.com/2022/08/04/cve-2022-35142-cve-2022-35143-cve-2022-35144"
},
{
"type": "WEB",
"url": "https://github.com/gilbitron/Raneto/releases"
},
{
"type": "PACKAGE",
"url": "https://github.com/ryanlelek/Raneto"
},
{
"type": "WEB",
"url": "https://github.com/ryanlelek/Raneto/releases/tag/0.17.1"
},
{
"type": "WEB",
"url": "http://raneto.com"
}
],
"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"
}
],
"summary": "Raneto Denial of Service via crafted payload injected into `Search` parameter"
}
GHSA-XXCH-H4GF-8FH3
Vulnerability from github – Published: 2022-05-17 03:59 – Updated: 2022-05-17 03:59Advantech EKI-132x devices with firmware before 2015-12-31 allow remote attackers to bypass authentication via unspecified vectors.
{
"affected": [],
"aliases": [
"CVE-2015-7938"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2016-01-09T02:59:00Z",
"severity": "CRITICAL"
},
"details": "Advantech EKI-132x devices with firmware before 2015-12-31 allow remote attackers to bypass authentication via unspecified vectors.",
"id": "GHSA-xxch-h4gf-8fh3",
"modified": "2022-05-17T03:59:36Z",
"published": "2022-05-17T03:59:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2015-7938"
},
{
"type": "WEB",
"url": "https://ics-cert.us-cert.gov/advisories/ICSA-15-344-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-XXMG-8G8R-G92F
Vulnerability from github – Published: 2023-03-28 21:30 – Updated: 2023-04-05 15:30Osprey Pump Controller version 1.01 could allow an unauthenticated user to create an account and bypass authentication, thereby gaining unauthorized access to the system. A threat actor could exploit this vulnerability to create a user account without providing valid credentials. A threat actor who successfully exploits this vulnerability could gain access to the pump controller and cause disruption in operation, modify data, or shut down the controller.
{
"affected": [],
"aliases": [
"CVE-2023-28398"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-03-28T21:15:00Z",
"severity": "CRITICAL"
},
"details": "Osprey Pump Controller version 1.01 could allow an unauthenticated user to create an account and bypass authentication, thereby gaining unauthorized access to the system. A threat actor could exploit this vulnerability to create a user account without providing valid credentials. A threat actor who successfully exploits this vulnerability could gain access to the pump controller and cause disruption in operation, modify data, or shut down the controller.",
"id": "GHSA-xxmg-8g8r-g92f",
"modified": "2023-04-05T15:30:25Z",
"published": "2023-03-28T21:30:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-28398"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-082-06"
}
],
"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"
}
]
}
GHSA-XXPF-83G5-3W2V
Vulnerability from github – Published: 2022-05-17 05:40 – Updated: 2022-05-17 05:40TCPUploadServer.exe in Progea Movicon 11.2 before Build 1084 does not require authentication for critical functions, which allows remote attackers to obtain sensitive information, delete files, execute arbitrary programs, or cause a denial of service (crash) via a crafted packet to TCP port 10651.
{
"affected": [],
"aliases": [
"CVE-2011-2963"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2011-07-29T19:55:00Z",
"severity": "HIGH"
},
"details": "TCPUploadServer.exe in Progea Movicon 11.2 before Build 1084 does not require authentication for critical functions, which allows remote attackers to obtain sensitive information, delete files, execute arbitrary programs, or cause a denial of service (crash) via a crafted packet to TCP port 10651.",
"id": "GHSA-xxpf-83g5-3w2v",
"modified": "2022-05-17T05:40:11Z",
"published": "2022-05-17T05:40:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2011-2963"
},
{
"type": "WEB",
"url": "http://www.exploit-db.com/exploits/17034"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/72888"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/46907"
},
{
"type": "WEB",
"url": "http://www.us-cert.gov/control_systems/pdf/ICSA-11-056-01.pdf"
},
{
"type": "WEB",
"url": "http://www.us-cert.gov/control_systems/pdf/ICSA-11-056-01A.pdf"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-XXPW-32HF-Q8V9
Vulnerability from github – Published: 2026-03-05 01:22 – Updated: 2026-03-06 14:24Summary
The official docker-compose.yml publishes the memcached service on host port 11211 (0.0.0.0:11211) with no authentication, while the Dockerfile configures PHP to store all user sessions in that memcached instance. An attacker who can reach port 11211 can read, modify, or flush session data — enabling session hijacking, admin impersonation, and mass session destruction without any application-level authentication.
Severity
High (CVSS 3.1: 8.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack Vector: Network —
docker-compose.ymlbinds memcached to0.0.0.0:11211on the host - Attack Complexity: High — exploitation requires port 11211 to be network-reachable, which depends on external firewall/security group configuration beyond the attacker's control
- Privileges Required: None — memcached has no authentication mechanism enabled
- User Interaction: None
- Scope: Unchanged — impact is to the AVideo application's session management
- Confidentiality Impact: High — session data includes user IDs, admin flags, email addresses, and password hashes
- Integrity Impact: High — an attacker can modify session data to inject admin privileges or impersonate any user
- Availability Impact: High —
flush_alldestroys all active sessions, forcing mass logout
Affected Component
docker-compose.yml— memcached serviceportsdirective (line 203)Dockerfile— PHP session configuration (lines 150-151)
CWE
- CWE-668: Exposure of Resource to Wrong Sphere
- CWE-287: Improper Authentication (memcached has no authentication)
Description
Memcached port unnecessarily published to host network
The docker-compose.yml publishes the memcached port to the Docker host's network interface:
# docker-compose.yml — lines 192-213
memcached:
image: memcached:alpine
restart: unless-stopped
command: >
memcached -m 512 -c 2048 -t ${NPROC:-4} -R 200
ports:
- "${MEMCACHE_PORT:-11211}:11211" # <-- Exposes to 0.0.0.0:11211
networks:
- app_net
The memcached command has no authentication flags:
- No -S flag (SASL authentication)
- No -l 127.0.0.1 flag (interface binding restriction)
The default env.example reinforces this port:
MEMCACHE_PORT=11211
PHP sessions stored entirely in memcached
The Dockerfile configures PHP to use memcached as the session store:
; Dockerfile — lines 150-151
session.save_handler = memcached
session.save_path = "memcached:11211?persistent=1&timeout=2&retry_interval=5"
Session data contains all authentication state
The application stores complete authentication state in sessions. From objects/user.php:
// user.php:1521 — login check
$isLogged = !empty($_SESSION['user']['id']);
// user.php:1544 — admin check
return !empty($_SESSION['user']['isAdmin']);
Session data includes: user ID, email, username, password hash, admin flag, channel name, photo URL, and email verification status (user.php lines 329-733). All of this is readable and writable via the exposed memcached port.
Inconsistent defense: database services are correctly internal-only
The docker-compose.yml demonstrates awareness of proper service isolation — both database services have NO ports: directive:
# docker-compose.yml — database service (lines 136-163)
database:
build:
context: .
dockerfile: Dockerfile.mariadb
# ... NO ports: directive — internal only
networks:
- app_net
# docker-compose.yml — database_encoder service (lines 165-189)
database_encoder:
build:
context: .
dockerfile: Dockerfile.mariadb
# ... NO ports: directive — internal only
networks:
- app_net
Both databases are only reachable via the internal app_net Docker network. Memcached — which stores equally sensitive session data — should follow the same pattern but does not. This inconsistency confirms the exposure is an oversight, not a design choice.
Port exposure map
| Service | Ports published to host | Contains sensitive data | Exposure justified |
|---|---|---|---|
| avideo | 80, 443, 2053 | N/A (web server) | Yes — serves web traffic |
| live | 1935, 8080, 8443 | N/A (streaming) | Yes — serves RTMP/HLS |
| database | None | Yes (all app data) | Correct — internal only |
| database_encoder | None | Yes (encoder data) | Correct — internal only |
| memcached | 11211 | Yes (all sessions) | No — should be internal only |
Execution chain
- Attacker scans the target host and discovers port 11211 is open
- Attacker connects with
nc TARGET 11211or any memcached client — no authentication required - Attacker runs
stats itemsto enumerate session slab classes - Attacker runs
stats cachedump <slab_id> <limit>to list session keys - Attacker runs
get <session_key>to read serialized PHP session data containing user IDs, admin flags, and password hashes - Attacker either:
- Hijacks a session: uses the session ID as a cookie to impersonate the user
- Escalates privileges: modifies session data to set
isAdminto true viaset <session_key> - Performs DoS: runs
flush_allto destroy all sessions
Proof of Concept
# 1. Verify memcached is reachable (returns server stats)
echo -e "stats\r" | nc TARGET 11211
# 2. Enumerate session keys
echo -e "stats items\r" | nc TARGET 11211
# Then for each slab:
echo -e "stats cachedump 1 100\r" | nc TARGET 11211
# 3. Read a session (key format: memc.sess.key.<session_id>)
echo -e "get memc.sess.key.abc123sessionid\r" | nc TARGET 11211
# Returns serialized PHP session with user data, admin flag, etc.
# 4. DoS — destroy all sessions (logs out every user)
echo -e "flush_all\r" | nc TARGET 11211
For session hijacking, extract the session ID from step 3 and set it as the PHPSESSID cookie in a browser to impersonate the victim user.
Impact
- Session hijacking: Read any user's session data and impersonate them by reusing their session ID — including admin accounts
- Privilege escalation: Modify session data to set
$_SESSION['user']['isAdmin']to a truthy value, granting admin access to any session - Credential exposure: Session data includes password hashes (
$_SESSION['user']['passhash'], user.php:555) that can be cracked offline - Mass session destruction:
flush_alldestroys all active sessions, forcing every logged-in user to re-authenticate — a one-command denial of service - Reconnaissance:
statsreveals server uptime, memory usage, connection counts, and cache hit/miss ratios
Recommended Remediation
Option 1: Remove the port mapping (preferred — one-line fix)
Memcached is only used internally by the PHP application via Docker networking. Remove the ports: directive entirely:
# docker-compose.yml — memcached service
memcached:
image: memcached:alpine
restart: unless-stopped
command: >
memcached -m 512 -c 2048 -t ${NPROC:-4} -R 200
# REMOVED: ports:
# - "${MEMCACHE_PORT:-11211}:11211"
deploy:
resources:
limits:
cpus: '1'
memory: "4G"
reservations:
cpus: '0.5'
memory: '1G'
networks:
- app_net
Also remove MEMCACHE_PORT=11211 from env.example since the port is no longer published.
The PHP application connects via the Docker internal hostname memcached:11211 (from session.save_path), which uses the app_net bridge network and does not require host-level port mapping.
Option 2: Bind memcached to localhost only (if host access is needed for debugging)
If host-level access to memcached is needed for debugging, bind only to the loopback interface:
ports:
- "127.0.0.1:${MEMCACHE_PORT:-11211}:11211"
This prevents remote access while allowing localhost:11211 connections from the Docker host.
Option 3: Enable SASL authentication (defense-in-depth)
Add SASL authentication to memcached as an additional layer:
command: >
memcached -m 512 -c 2048 -t ${NPROC:-4} -R 200 -S
environment:
MEMCACHED_USERNAME: "${MEMCACHED_USER:-avideo}"
MEMCACHED_PASSWORD: "${MEMCACHED_PASSWORD}"
Update the PHP session configuration accordingly:
session.save_path = "PERSISTENT=myapp avideo:${MEMCACHED_PASSWORD}@memcached:11211"
Note: Option 1 alone is sufficient and should be applied immediately. Options 2 and 3 provide defense-in-depth.
Credit
This vulnerability was discovered and reported by bugbunny.ai.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "wwbn/avideo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "21.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-29093"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-668"
],
"github_reviewed": true,
"github_reviewed_at": "2026-03-05T01:22:21Z",
"nvd_published_at": "2026-03-06T04:16:08Z",
"severity": "HIGH"
},
"details": "## Summary\nThe official `docker-compose.yml` publishes the memcached service on host port 11211 (`0.0.0.0:11211`) with no authentication, while the Dockerfile configures PHP to store all user sessions in that memcached instance. An attacker who can reach port 11211 can read, modify, or flush session data \u2014 enabling session hijacking, admin impersonation, and mass session destruction without any application-level authentication.\n\n## Severity\n**High** (CVSS 3.1: 8.1)\n\n`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`\n\n- **Attack Vector:** Network \u2014 `docker-compose.yml` binds memcached to `0.0.0.0:11211` on the host\n- **Attack Complexity:** High \u2014 exploitation requires port 11211 to be network-reachable, which depends on external firewall/security group configuration beyond the attacker\u0027s control\n- **Privileges Required:** None \u2014 memcached has no authentication mechanism enabled\n- **User Interaction:** None\n- **Scope:** Unchanged \u2014 impact is to the AVideo application\u0027s session management\n- **Confidentiality Impact:** High \u2014 session data includes user IDs, admin flags, email addresses, and password hashes\n- **Integrity Impact:** High \u2014 an attacker can modify session data to inject admin privileges or impersonate any user\n- **Availability Impact:** High \u2014 `flush_all` destroys all active sessions, forcing mass logout\n\n## Affected Component\n- `docker-compose.yml` \u2014 memcached service `ports` directive (line 203)\n- `Dockerfile` \u2014 PHP session configuration (lines 150-151)\n\n## CWE\n- **CWE-668**: Exposure of Resource to Wrong Sphere\n- **CWE-287**: Improper Authentication (memcached has no authentication)\n\n## Description\n\n### Memcached port unnecessarily published to host network\n\nThe `docker-compose.yml` publishes the memcached port to the Docker host\u0027s network interface:\n\n```yaml\n# docker-compose.yml \u2014 lines 192-213\n memcached:\n image: memcached:alpine\n restart: unless-stopped\n command: \u003e\n memcached -m 512 -c 2048 -t ${NPROC:-4} -R 200\n ports:\n - \"${MEMCACHE_PORT:-11211}:11211\" # \u003c-- Exposes to 0.0.0.0:11211\n networks:\n - app_net\n```\n\nThe memcached command has no authentication flags:\n- No `-S` flag (SASL authentication)\n- No `-l 127.0.0.1` flag (interface binding restriction)\n\nThe default `env.example` reinforces this port:\n```\nMEMCACHE_PORT=11211\n```\n\n### PHP sessions stored entirely in memcached\n\nThe Dockerfile configures PHP to use memcached as the session store:\n\n```ini\n; Dockerfile \u2014 lines 150-151\nsession.save_handler = memcached\nsession.save_path = \"memcached:11211?persistent=1\u0026timeout=2\u0026retry_interval=5\"\n```\n\n### Session data contains all authentication state\n\nThe application stores complete authentication state in sessions. From `objects/user.php`:\n\n```php\n// user.php:1521 \u2014 login check\n$isLogged = !empty($_SESSION[\u0027user\u0027][\u0027id\u0027]);\n\n// user.php:1544 \u2014 admin check\nreturn !empty($_SESSION[\u0027user\u0027][\u0027isAdmin\u0027]);\n```\n\nSession data includes: user ID, email, username, password hash, admin flag, channel name, photo URL, and email verification status (user.php lines 329-733). All of this is readable and writable via the exposed memcached port.\n\n### Inconsistent defense: database services are correctly internal-only\n\nThe `docker-compose.yml` demonstrates awareness of proper service isolation \u2014 both database services have NO `ports:` directive:\n\n```yaml\n# docker-compose.yml \u2014 database service (lines 136-163)\n database:\n build:\n context: .\n dockerfile: Dockerfile.mariadb\n # ... NO ports: directive \u2014 internal only\n networks:\n - app_net\n\n# docker-compose.yml \u2014 database_encoder service (lines 165-189)\n database_encoder:\n build:\n context: .\n dockerfile: Dockerfile.mariadb\n # ... NO ports: directive \u2014 internal only\n networks:\n - app_net\n```\n\nBoth databases are only reachable via the internal `app_net` Docker network. Memcached \u2014 which stores equally sensitive session data \u2014 should follow the same pattern but does not. This inconsistency confirms the exposure is an oversight, not a design choice.\n\n### Port exposure map\n\n| Service | Ports published to host | Contains sensitive data | Exposure justified |\n|---------|------------------------|------------------------|--------------------|\n| avideo | 80, 443, 2053 | N/A (web server) | Yes \u2014 serves web traffic |\n| live | 1935, 8080, 8443 | N/A (streaming) | Yes \u2014 serves RTMP/HLS |\n| database | None | Yes (all app data) | Correct \u2014 internal only |\n| database_encoder | None | Yes (encoder data) | Correct \u2014 internal only |\n| **memcached** | **11211** | **Yes (all sessions)** | **No \u2014 should be internal only** |\n\n### Execution chain\n\n1. Attacker scans the target host and discovers port 11211 is open\n2. Attacker connects with `nc TARGET 11211` or any memcached client \u2014 no authentication required\n3. Attacker runs `stats items` to enumerate session slab classes\n4. Attacker runs `stats cachedump \u003cslab_id\u003e \u003climit\u003e` to list session keys\n5. Attacker runs `get \u003csession_key\u003e` to read serialized PHP session data containing user IDs, admin flags, and password hashes\n6. Attacker either:\n - **Hijacks a session**: uses the session ID as a cookie to impersonate the user\n - **Escalates privileges**: modifies session data to set `isAdmin` to true via `set \u003csession_key\u003e`\n - **Performs DoS**: runs `flush_all` to destroy all sessions\n\n## Proof of Concept\n\n```bash\n# 1. Verify memcached is reachable (returns server stats)\necho -e \"stats\\r\" | nc TARGET 11211\n\n# 2. Enumerate session keys\necho -e \"stats items\\r\" | nc TARGET 11211\n# Then for each slab:\necho -e \"stats cachedump 1 100\\r\" | nc TARGET 11211\n\n# 3. Read a session (key format: memc.sess.key.\u003csession_id\u003e)\necho -e \"get memc.sess.key.abc123sessionid\\r\" | nc TARGET 11211\n# Returns serialized PHP session with user data, admin flag, etc.\n\n# 4. DoS \u2014 destroy all sessions (logs out every user)\necho -e \"flush_all\\r\" | nc TARGET 11211\n```\n\nFor session hijacking, extract the session ID from step 3 and set it as the `PHPSESSID` cookie in a browser to impersonate the victim user.\n\n## Impact\n\n- **Session hijacking**: Read any user\u0027s session data and impersonate them by reusing their session ID \u2014 including admin accounts\n- **Privilege escalation**: Modify session data to set `$_SESSION[\u0027user\u0027][\u0027isAdmin\u0027]` to a truthy value, granting admin access to any session\n- **Credential exposure**: Session data includes password hashes (`$_SESSION[\u0027user\u0027][\u0027passhash\u0027]`, user.php:555) that can be cracked offline\n- **Mass session destruction**: `flush_all` destroys all active sessions, forcing every logged-in user to re-authenticate \u2014 a one-command denial of service\n- **Reconnaissance**: `stats` reveals server uptime, memory usage, connection counts, and cache hit/miss ratios\n\n## Recommended Remediation\n\n### Option 1: Remove the port mapping (preferred \u2014 one-line fix)\n\nMemcached is only used internally by the PHP application via Docker networking. Remove the `ports:` directive entirely:\n\n```yaml\n# docker-compose.yml \u2014 memcached service\n memcached:\n image: memcached:alpine\n restart: unless-stopped\n command: \u003e\n memcached -m 512 -c 2048 -t ${NPROC:-4} -R 200\n # REMOVED: ports:\n # - \"${MEMCACHE_PORT:-11211}:11211\"\n deploy:\n resources:\n limits:\n cpus: \u00271\u0027\n memory: \"4G\"\n reservations:\n cpus: \u00270.5\u0027\n memory: \u00271G\u0027\n networks:\n - app_net\n```\n\nAlso remove `MEMCACHE_PORT=11211` from `env.example` since the port is no longer published.\n\nThe PHP application connects via the Docker internal hostname `memcached:11211` (from `session.save_path`), which uses the `app_net` bridge network and does not require host-level port mapping.\n\n### Option 2: Bind memcached to localhost only (if host access is needed for debugging)\n\nIf host-level access to memcached is needed for debugging, bind only to the loopback interface:\n\n```yaml\n ports:\n - \"127.0.0.1:${MEMCACHE_PORT:-11211}:11211\"\n```\n\nThis prevents remote access while allowing `localhost:11211` connections from the Docker host.\n\n### Option 3: Enable SASL authentication (defense-in-depth)\n\nAdd SASL authentication to memcached as an additional layer:\n\n```yaml\n command: \u003e\n memcached -m 512 -c 2048 -t ${NPROC:-4} -R 200 -S\n environment:\n MEMCACHED_USERNAME: \"${MEMCACHED_USER:-avideo}\"\n MEMCACHED_PASSWORD: \"${MEMCACHED_PASSWORD}\"\n```\n\nUpdate the PHP session configuration accordingly:\n```ini\nsession.save_path = \"PERSISTENT=myapp avideo:${MEMCACHED_PASSWORD}@memcached:11211\"\n```\n\n**Note:** Option 1 alone is sufficient and should be applied immediately. Options 2 and 3 provide defense-in-depth.\n\n## Credit\nThis vulnerability was discovered and reported by [bugbunny.ai](https://bugbunny.ai).",
"id": "GHSA-xxpw-32hf-q8v9",
"modified": "2026-03-06T14:24:08Z",
"published": "2026-03-05T01:22:21Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/security/advisories/GHSA-xxpw-32hf-q8v9"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-29093"
},
{
"type": "PACKAGE",
"url": "https://github.com/WWBN/AVideo"
},
{
"type": "WEB",
"url": "https://github.com/WWBN/AVideo/releases/tag/24.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "AVideo: Unauthenticated PHP session store exposed to host network via published memcached port"
}
GHSA-XXR8-RX47-Q5RR
Vulnerability from github – Published: 2022-05-01 07:10 – Updated: 2025-04-03 04:38Session fixation vulnerability in Jetbox CMS 2.1 SR1 allows remote attackers to hijack web sessions via a crafted link and the administrator section.
{
"affected": [],
"aliases": [
"CVE-2006-3583"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2006-08-08T23:04:00Z",
"severity": "HIGH"
},
"details": "Session fixation vulnerability in Jetbox CMS 2.1 SR1 allows remote attackers to hijack web sessions via a crafted link and the administrator section.",
"id": "GHSA-xxr8-rx47-q5rr",
"modified": "2025-04-03T04:38:06Z",
"published": "2022-05-01T07:10:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2006-3583"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/20889"
},
{
"type": "WEB",
"url": "http://secunia.com/secunia_research/2006-57/advisory"
},
{
"type": "WEB",
"url": "http://securityreason.com/securityalert/1339"
},
{
"type": "WEB",
"url": "http://www.osvdb.org/27710"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/441980/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/19303"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-XXV4-76MP-4WM8
Vulnerability from github – Published: 2022-08-12 00:01 – Updated: 2022-08-16 00:00A vulnerability was found in SourceCodester Company Website CMS 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /dashboard/settings. The manipulation leads to improper authentication. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-206161 was assigned to this vulnerability.
{
"affected": [],
"aliases": [
"CVE-2022-2765"
],
"database_specific": {
"cwe_ids": [
"CWE-287",
"CWE-306"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-08-11T10:15:00Z",
"severity": "CRITICAL"
},
"details": "A vulnerability was found in SourceCodester Company Website CMS 1.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /dashboard/settings. The manipulation leads to improper authentication. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-206161 was assigned to this vulnerability.",
"id": "GHSA-xxv4-76mp-4wm8",
"modified": "2022-08-16T00:00:26Z",
"published": "2022-08-12T00:01:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-2765"
},
{
"type": "WEB",
"url": "https://github.com/ch0ing/vul/blob/main/WebRay.com.cn/Company%20Website%20CMS--.md"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.206161"
}
],
"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"
}
]
}
GHSA-XXW3-765M-F37P
Vulnerability from github – Published: 2022-05-24 17:43 – Updated: 2024-10-23 18:24An issue was discovered in through SaltStack Salt before 3002.5. salt-api does not honor eauth credentials for the wheel_async client. Thus, an attacker can remotely run any wheel modules on the master.
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2015.8.13"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "2016.3.0"
},
{
"fixed": "2016.11.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "2016.11.7"
},
{
"fixed": "2016.11.10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "2017.5.0"
},
{
"fixed": "2017.7.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "2018.2.0"
},
{
"last_affected": "2018.3.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "2019.2.0"
},
{
"fixed": "2019.2.8"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "3000"
},
{
"fixed": "3000.7"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "3001"
},
{
"fixed": "3001.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "PyPI",
"name": "salt"
},
"ranges": [
{
"events": [
{
"introduced": "3002"
},
{
"fixed": "3002.3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-25281"
],
"database_specific": {
"cwe_ids": [
"CWE-287"
],
"github_reviewed": true,
"github_reviewed_at": "2024-04-22T21:17:10Z",
"nvd_published_at": "2021-02-27T05:15:00Z",
"severity": "CRITICAL"
},
"details": "An issue was discovered in through SaltStack Salt before 3002.5. salt-api does not honor eauth credentials for the wheel_async client. Thus, an attacker can remotely run any wheel modules on the master.",
"id": "GHSA-xxw3-765m-f37p",
"modified": "2024-10-23T18:24:01Z",
"published": "2022-05-24T17:43:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-25281"
},
{
"type": "WEB",
"url": "https://www.saltstack.com/blog/active-saltstack-cve-announced-2021-jan-21"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2021/dsa-5011"
},
{
"type": "WEB",
"url": "https://security.gentoo.org/glsa/202310-22"
},
{
"type": "WEB",
"url": "https://security.gentoo.org/glsa/202103-01"
},
{
"type": "WEB",
"url": "https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YOGNT2XWPOYV7YT75DN7PS4GIYWFKOK5"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FUGLOJ6NXLCIFRD2JTXBYQEMAEF2B6XH"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7GRVZ5WAEI3XFN2BDTL6DDXFS5HYSDVB"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YOGNT2XWPOYV7YT75DN7PS4GIYWFKOK5"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FUGLOJ6NXLCIFRD2JTXBYQEMAEF2B6XH"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/7GRVZ5WAEI3XFN2BDTL6DDXFS5HYSDVB"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2021/11/msg00009.html"
},
{
"type": "WEB",
"url": "https://github.com/saltstack/salt/releases"
},
{
"type": "WEB",
"url": "https://github.com/saltstack/salt/blob/8f9405cf8e6f7d7776d5000841c886dec6d96250/doc/topics/releases/3002.3.rst#L28"
},
{
"type": "WEB",
"url": "https://github.com/saltstack/salt/blob/8f9405cf8e6f7d7776d5000841c886dec6d96250/doc/topics/releases/3001.5.rst#L28"
},
{
"type": "WEB",
"url": "https://github.com/saltstack/salt/blob/8f9405cf8e6f7d7776d5000841c886dec6d96250/doc/topics/releases/3000.7.rst#L28"
},
{
"type": "PACKAGE",
"url": "https://github.com/saltstack/salt"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/salt/PYSEC-2021-50.yaml"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/162058/SaltStack-Salt-API-Unauthenticated-Remote-Command-Execution.html"
}
],
"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"
}
],
"summary": "SaltStack Salt Improper Authentication vulnerability"
}
Mitigation
Strategy: Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
CAPEC-114: Authentication Abuse
An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.
CAPEC-115: Authentication Bypass
An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.
CAPEC-151: Identity Spoofing
Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.
CAPEC-194: Fake the Source of Data
An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.
CAPEC-22: Exploiting Trust in Client
An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
CAPEC-57: Utilizing REST's Trust in the System Resource to Obtain Sensitive Data
This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.
CAPEC-593: Session Hijacking
This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.
CAPEC-633: Token Impersonation
An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.
CAPEC-650: Upload a Web Shell to a Web Server
By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.
CAPEC-94: Adversary in the Middle (AiTM)
An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.