Common Weakness Enumeration
CWE-693
DiscouragedProtection Mechanism Failure
Abstraction: Pillar · Status: Draft
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
1256 vulnerabilities reference this CWE, most recent first.
GCVE-1988-2026-0099
Vulnerability from gna-1988 – Published: 2026-09-07 13:20 – Updated: 2026-09-11 11:35
VLAI
EPSS
VEX
Title
OpenBlow Multiple Deanonymization Vulnerabilities
Summary
OpenBlow Multiple Deanonymization Vulnerabilities
Summary
A production deployment was observed (HTTP archive of a full, real whistleblower
submission) to route its anonymous reporting flow through Google. The intake
CAPTCHA is Google reCAPTCHA, enforced as a mandatory, server-validated gate
on report submission, and the UI additionally pulls a web font from
fonts.gstatic.com. As a result, every prospective whistleblower's browser
makes direct connections to www.google.com and www.gstatic.com before a
report can be filed, disclosing the reporter's source IP, browser fingerprint,
and the precise identity of the whistleblowing site to a third party. The
absence
of a Content-Security-Policy and Referrer-Policy is what permits these
cross-origin loads.
The defects, in severity order:
1. (Critical) Google reCAPTCHA is a mandatory gate on the anonymous
submission flow - a whistleblower cannot submit without first being exposed to
Google.
2. (High) A web font is loaded from fonts.gstatic.com, a second independent
IP/fingerprint disclosure to Google.
3. (Medium) No Content-Security-Policy and no Referrer-Policy on
responses, which is what allows the third-party loads above.
Component
deployment / configuration
Classification
valid
Evidence: HAR capture of one end-to-end flow (load intake → upload attachments →
POST /api/v0/whistleblower/tip → retrieve). The submission could not complete
without a Google reCAPTCHA token, which is present in the submission body and is
produced only after live calls to Google.
Details
Hosts contacted during a single anonymous submission:
(first-party API + assets)
www.google.com (reCAPTCHA: api.js, api2/anchor, api2/reload [POST], …)
www.gstatic.com (reCAPTCHA static bundle)
fonts.gstatic.com (Roboto .woff2 web font)
Submission endpoint:
POST /api/v0/whistleblower/tip
request body field "captcha" carries a Google reCAPTCHA token:
"captcha":"0cAFcWeA4BGSN1zd5E_vRIN…"
-> the token is required and server-validated: submission is gated on Google.
Site identity leaked to Google (reCAPTCHA anchor "co" parameter, base64):
co -> decodes to https://:443
1. (Critical) Mandatory Google reCAPTCHA on the anonymous intake path
The submission request carries a Google reCAPTCHA token in the captcha field of
the POST /api/v0/whistleblower/tip body, and that token can only be obtained
after the browser performs the reCAPTCHA handshake with Google (api.js →
api2/anchor → api2/reload). The flow therefore cannot proceed without
contacting Google.
Google consequently receives, for every prospective reporter:
- the source IP address of the whistleblower's browser;
- a browser/device fingerprint (reCAPTCHA's purpose is behavioural/device
scoring);
- the exact whistleblowing site being used - the reCAPTCHA co parameter
base64-encodes the full origin (https://:443).
This contradicts the platform's anonymity guarantee, under which no third party
must be able to learn the identity of a source. It also degrades Tor usability:
reCAPTCHA routinely blocks or challenges Tor exit nodes, pushing at-risk users
off Tor toward non-anonymous access.
2. (High) Web font served from fonts.gstatic.com
Independently of reCAPTCHA, the UI fetches a Roboto .woff2 from
fonts.gstatic.com - a second, separate disclosure of the reporter's IP to
Google on the same pages.
3. (Medium) Missing Content-Security-Policy and Referrer-Policy
None of the captured first-party responses carry a Content-Security-Policy or a
Referrer-Policy. The absence of a restrictive CSP is what permits the
cross-origin Google/gstatic loads in findings 1–2; a correct CSP would have
blocked them.
Observed first-party response headers (representative):
strict-transport-security: max-age=31536000; includeSubDomains # present
x-frame-options: SAMEORIGIN # present
x-content-type-options: nosniff # present
access-control-allow-origin: https:// # scoped
(no content-security-policy) # MISSING
(no referrer-policy) # MISSING
PoC
Steps to reproduce
From a HAR capture (or live DevTools → Network) of the submission flow:
# Confirm the gate is mandatory and server-validated - the submission body
# contains a Google reCAPTCHA token:
python3 - <<'PY'
import json
har = json.load(open(".har"))
for e in har["log"]["entries"]:
if "/whistleblower/tip?" in e["request"]["url"]:
b = json.loads(e["request"]["postData"]["text"])
print("captcha token present:", bool(b.get("captcha")))
PY
# Confirm the site identity is leaked to Google (anchor "co" param):
python3 - <<'PY'
import base64, urllib.parse as u, json
har = json.load(open(".har"))
for e in har["log"]["entries"]:
q = u.parse_qs(u.urlparse(e["request"]["url"]).query)
if "co" in q:
print(base64.b64decode(q["co"][0] + "==").decode("utf-8", "replace"))
PY
Expected result
An anonymous reporting flow must complete without the reporter's browser
contacting any third party. The CAPTCHA must be an offline, first-party
challenge;
all fonts/assets must be first-party; a strict CSP must prevent any cross-origin
script/font load.
Actual result
The submission cannot complete without a Google reCAPTCHA token; obtaining it
requires live connections to www.google.com/www.gstatic.com, and a web font is
fetched from fonts.gstatic.com. Google receives the reporter's IP, a device
fingerprint, and the exact site origin (https://:443). No
CSP/Referrer-Policy is present to prevent this.
Impact
A whistleblowing platform's central promise is that a source cannot be
identified
by any third party. This deployment forces every prospective source to disclose
their IP address, a browser/device fingerprint, and the precise identity of the
channel they are using to Google - as a mandatory precondition of filing a
report. An adversary with visibility into, or legal reach over, that third party
can correlate "who contacted reCAPTCHA for this specific whistleblowing origin,
from which IP, at what time" with the subsequently received report. The
Tor-hostility of reCAPTCHA compounds this.
Potential impact:
- Confidentiality: High (source deanonymization via third-party IP/fingerprint +
site-identity disclosure on the anonymous intake path).
- Integrity: None.
- Availability: Low (reCAPTCHA/Tor friction can block legitimate anonymous
submissions).
Remediation
1. Disable Google reCAPTCHA; use an offline, first-party CAPTCHA. The intake
flow must never depend on a third party.
2. Self-host all fonts and assets; remove fonts.gstatic.com (and any other
third-party origin) from the served pages.
3. Deploy a strict Content-Security-Policy (default-src 'self', no
third-party script-src/font-src/connect-src) and a hardened
Referrer-Policy (e.g. no-referrer), so third-party loads are structurally
impossible.
Severity
Critical. The defects require no privileges and no user interaction beyond a
victim attempting to use the platform for its intended purpose, are exploitable
by
a network/third-party observer, and defeat the platform's primary security
property (source anonymity) on the anonymous intake path (Scope: Changed).
Vector string
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L
Weaknesses
Common Weakness Enumerator CWE:
- CWE-359 - Exposure of Private Personal Information to an Unauthorized Actor
- CWE-829 - Inclusion of Functionality from Untrusted Control Sphere
- CWE-693 - Protection Mechanism Failure
- Missing Content-Security-Policy enabling the third-party loads
_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
5 references
| URL | Tags |
|---|---|
| https://vuln.freearchive.org/archive/full-disclos… | technical-descriptionexploit |
| https://seclists.org/fulldisclosure/2026/Jul/15 | technical-description |
| https://:443 | |
| https://nmap.org/mailman/listinfo/fulldisclosure | |
| https://seclists.org/fulldisclosure/ |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| Laser Romae S.R.L. | Openblow |
Affected:
unknown
|
{
"containers": {
"cna": {
"affected": [
{
"product": "Openblow",
"vendor": "Laser Romae\u202fS.R.L.",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Red Nanaki via Fulldisclosure"
}
],
"descriptions": [
{
"lang": "en",
"value": "OpenBlow Multiple Deanonymization Vulnerabilities\n\nSummary\n\nA production deployment was observed (HTTP archive of a full, real whistleblower\nsubmission) to route its anonymous reporting flow through Google. The intake\nCAPTCHA is Google reCAPTCHA, enforced as a mandatory, server-validated gate\non report submission, and the UI additionally pulls a web font from\nfonts.gstatic.com. As a result, every prospective whistleblower\u0027s browser\nmakes direct connections to www.google.com and www.gstatic.com before a\nreport can be filed, disclosing the reporter\u0027s source IP, browser fingerprint,\nand the precise identity of the whistleblowing site to a third party. The\nabsence\nof a Content-Security-Policy and Referrer-Policy is what permits these\ncross-origin loads.\n\nThe defects, in severity order:\n\n1. (Critical) Google reCAPTCHA is a mandatory gate on the anonymous\nsubmission flow - a whistleblower cannot submit without first being exposed to\nGoogle.\n2. (High) A web font is loaded from fonts.gstatic.com, a second independent\nIP/fingerprint disclosure to Google.\n3. (Medium) No Content-Security-Policy and no Referrer-Policy on\nresponses, which is what allows the third-party loads above.\n\nComponent\n\ndeployment / configuration\n\nClassification\n\nvalid\n\nEvidence: HAR capture of one end-to-end flow (load intake \u2192 upload attachments \u2192\nPOST /api/v0/whistleblower/tip \u2192 retrieve). The submission could not complete\nwithout a Google reCAPTCHA token, which is present in the submission body and is\nproduced only after live calls to Google.\n\nDetails\n\nHosts contacted during a single anonymous submission:\n(first-party API + assets)\nwww.google.com (reCAPTCHA: api.js, api2/anchor, api2/reload [POST], \u2026)\nwww.gstatic.com (reCAPTCHA static bundle)\nfonts.gstatic.com (Roboto .woff2 web font)\n\nSubmission endpoint:\nPOST /api/v0/whistleblower/tip\nrequest body field \"captcha\" carries a Google reCAPTCHA token:\n\"captcha\":\"0cAFcWeA4BGSN1zd5E_vRIN\u2026\"\n-\u003e the token is required and server-validated: submission is gated on Google.\n\nSite identity leaked to Google (reCAPTCHA anchor \"co\" parameter, base64):\nco -\u003e decodes to https://:443\n\n1. (Critical) Mandatory Google reCAPTCHA on the anonymous intake path\n\nThe submission request carries a Google reCAPTCHA token in the captcha field of\nthe POST /api/v0/whistleblower/tip body, and that token can only be obtained\nafter the browser performs the reCAPTCHA handshake with Google (api.js \u2192\napi2/anchor \u2192 api2/reload). The flow therefore cannot proceed without\ncontacting Google.\n\nGoogle consequently receives, for every prospective reporter:\n\n- the source IP address of the whistleblower\u0027s browser;\n- a browser/device fingerprint (reCAPTCHA\u0027s purpose is behavioural/device\nscoring);\n- the exact whistleblowing site being used - the reCAPTCHA co parameter\nbase64-encodes the full origin (https://:443).\n\nThis contradicts the platform\u0027s anonymity guarantee, under which no third party\nmust be able to learn the identity of a source. It also degrades Tor usability:\nreCAPTCHA routinely blocks or challenges Tor exit nodes, pushing at-risk users\noff Tor toward non-anonymous access.\n\n2. (High) Web font served from fonts.gstatic.com\n\nIndependently of reCAPTCHA, the UI fetches a Roboto .woff2 from\nfonts.gstatic.com - a second, separate disclosure of the reporter\u0027s IP to\nGoogle on the same pages.\n\n3. (Medium) Missing Content-Security-Policy and Referrer-Policy\n\nNone of the captured first-party responses carry a Content-Security-Policy or a\nReferrer-Policy. The absence of a restrictive CSP is what permits the\ncross-origin Google/gstatic loads in findings 1\u20132; a correct CSP would have\nblocked them.\n\nObserved first-party response headers (representative):\n\nstrict-transport-security: max-age=31536000; includeSubDomains # present\nx-frame-options: SAMEORIGIN # present\nx-content-type-options: nosniff # present\naccess-control-allow-origin: https:// # scoped\n(no content-security-policy) # MISSING\n(no referrer-policy) # MISSING\n\nPoC\n\nSteps to reproduce\n\nFrom a HAR capture (or live DevTools \u2192 Network) of the submission flow:\n\n# Confirm the gate is mandatory and server-validated - the submission body\n# contains a Google reCAPTCHA token:\npython3 - \u003c\u003c\u0027PY\u0027\nimport json\nhar = json.load(open(\".har\"))\nfor e in har[\"log\"][\"entries\"]:\nif \"/whistleblower/tip?\" in e[\"request\"][\"url\"]:\nb = json.loads(e[\"request\"][\"postData\"][\"text\"])\nprint(\"captcha token present:\", bool(b.get(\"captcha\")))\nPY\n\n# Confirm the site identity is leaked to Google (anchor \"co\" param):\npython3 - \u003c\u003c\u0027PY\u0027\nimport base64, urllib.parse as u, json\nhar = json.load(open(\".har\"))\nfor e in har[\"log\"][\"entries\"]:\nq = u.parse_qs(u.urlparse(e[\"request\"][\"url\"]).query)\nif \"co\" in q:\nprint(base64.b64decode(q[\"co\"][0] + \"==\").decode(\"utf-8\", \"replace\"))\nPY\n\nExpected result\n\nAn anonymous reporting flow must complete without the reporter\u0027s browser\ncontacting any third party. The CAPTCHA must be an offline, first-party\nchallenge;\nall fonts/assets must be first-party; a strict CSP must prevent any cross-origin\nscript/font load.\n\nActual result\n\nThe submission cannot complete without a Google reCAPTCHA token; obtaining it\nrequires live connections to www.google.com/www.gstatic.com, and a web font is\nfetched from fonts.gstatic.com. Google receives the reporter\u0027s IP, a device\nfingerprint, and the exact site origin (https://:443). No\nCSP/Referrer-Policy is present to prevent this.\n\nImpact\n\nA whistleblowing platform\u0027s central promise is that a source cannot be\nidentified\nby any third party. This deployment forces every prospective source to disclose\ntheir IP address, a browser/device fingerprint, and the precise identity of the\nchannel they are using to Google - as a mandatory precondition of filing a\nreport. An adversary with visibility into, or legal reach over, that third party\ncan correlate \"who contacted reCAPTCHA for this specific whistleblowing origin,\nfrom which IP, at what time\" with the subsequently received report. The\nTor-hostility of reCAPTCHA compounds this.\n\nPotential impact:\n\n- Confidentiality: High (source deanonymization via third-party IP/fingerprint +\nsite-identity disclosure on the anonymous intake path).\n- Integrity: None.\n- Availability: Low (reCAPTCHA/Tor friction can block legitimate anonymous\nsubmissions).\n\nRemediation\n\n1. Disable Google reCAPTCHA; use an offline, first-party CAPTCHA. The intake\nflow must never depend on a third party.\n2. Self-host all fonts and assets; remove fonts.gstatic.com (and any other\nthird-party origin) from the served pages.\n3. Deploy a strict Content-Security-Policy (default-src \u0027self\u0027, no\nthird-party script-src/font-src/connect-src) and a hardened\nReferrer-Policy (e.g. no-referrer), so third-party loads are structurally\nimpossible.\n\nSeverity\n\nCritical. The defects require no privileges and no user interaction beyond a\nvictim attempting to use the platform for its intended purpose, are exploitable\nby\na network/third-party observer, and defeat the platform\u0027s primary security\nproperty (source anonymity) on the anonymous intake path (Scope: Changed).\n\nVector string\n\nCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:L\n\nWeaknesses\n\nCommon Weakness Enumerator CWE:\n\n- CWE-359 - Exposure of Private Personal Information to an Unauthorized Actor\n- CWE-829 - Inclusion of Functionality from Untrusted Control Sphere\n- CWE-693 - Protection Mechanism Failure\n- Missing Content-Security-Policy enabling the third-party loads\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-359",
"description": "CWE-359",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-693",
"description": "CWE-693",
"lang": "en",
"type": "CWE"
},
{
"cweId": "CWE-829",
"description": "CWE-829",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-09-11T11:35:28Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description",
"exploit"
],
"url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jul/15"
},
{
"tags": [
"technical-description"
],
"url": "https://seclists.org/fulldisclosure/2026/Jul/15"
},
{
"url": "https://:443"
},
{
"url": "https://nmap.org/mailman/listinfo/fulldisclosure"
},
{
"url": "https://seclists.org/fulldisclosure/"
}
],
"source": {
"defect": [
"https://seclists.org/fulldisclosure/2026/Jul/15"
],
"discovery": "EXTERNAL"
},
"title": "OpenBlow Multiple Deanonymization Vulnerabilities",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0099",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jul/15",
"automated": true,
"contentSha256": "744175a5c223244ab1e223a2db5ad49da8d33cfee9f3f874cb3d0ccc5f637505",
"evidenceScore": 11,
"messageId": "",
"originalUrl": "https://seclists.org/fulldisclosure/2026/Jul/15",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-06-21T10:16:53Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-09-07T13:20:22Z",
"dateUpdated": "2026-09-11T11:35:28Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0099"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-71373 (GCVE-0-2025-71373)
Vulnerability from cvelistv5 – Published: 2026-07-04 01:23 – Updated: 2026-07-06 18:16
VLAI
EPSS
VEX
Title
picklescan - Remote Code Execution via operator.methodcaller Detection Bypass
Summary
picklescan before 0.0.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle payloads using operator.methodcaller that execute arbitrary code when loaded, compromising systems relying on picklescan for validation.
Severity
SSVC
Exploitation: poc
Automatable: no
Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-07-06 18:16 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
2 references
| URL | Tags |
|---|---|
| https://github.com/mmaitre314/picklescan/security… | vendor-advisory |
| https://www.vulncheck.com/advisories/picklescan-r… | third-party-advisory |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| picklescan | picklescan |
Affected:
0 , < 0.0.33
(semver)
Unaffected: 0.0.33 (semver) cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:* |
Date Public
2025-12-27 00:00
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-71373",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-06T18:16:30.815234Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-06T18:16:45.056Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-x843-g5mx-g377"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:pypi/picklescan",
"product": "picklescan",
"vendor": "picklescan",
"versions": [
{
"lessThan": "0.0.33",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "0.0.33",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*",
"versionEndExcluding": "0.0.33",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "CoolwindHF"
}
],
"datePublic": "2025-12-27T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "picklescan before 0.0.33 fails to detect operator.methodcaller function calls in pickle files, allowing attackers to bypass security checks. Remote attackers can craft malicious pickle payloads using operator.methodcaller that execute arbitrary code when loaded, compromising systems relying on picklescan for validation."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 7.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-07-04T01:23:41.446Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-x843-g5mx-g377)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-x843-g5mx-g377"
},
{
"name": "VulnCheck Advisory: picklescan - Remote Code Execution via operator.methodcaller Detection Bypass",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-operator-methodcaller-detection-bypass"
}
],
"title": "picklescan - Remote Code Execution via operator.methodcaller Detection Bypass",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2025-71373",
"datePublished": "2026-07-04T01:23:41.446Z",
"dateReserved": "2026-06-20T13:11:44.727Z",
"dateUpdated": "2026-07-06T18:16:45.056Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-71352 (GCVE-0-2025-71352)
Vulnerability from cvelistv5 – Published: 2026-06-30 22:08 – Updated: 2026-07-01 13:20
VLAI
EPSS
VEX
Title
picklescan - Remote Code Execution via Undetected trace.Trace.runctx in Pickle Files
Summary
picklescan before 0.0.29 fails to detect the built-in Python trace.Trace.runctx function when used in pickle file reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files with trace.Trace.runctx payloads that bypass picklescan detection and execute code upon pickle.load() invocation.
Severity
SSVC
Exploitation: poc
Automatable: no
Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-07-01 13:19 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
2 references
| URL | Tags |
|---|---|
| https://github.com/mmaitre314/picklescan/security… | vendor-advisory |
| https://www.vulncheck.com/advisories/picklescan-r… | third-party-advisory |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| picklescan | picklescan |
Affected:
0 , < 0.0.29
(semver)
Unaffected: 0.0.29 (semver) cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:* |
Date Public
2025-08-26 00:00
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-71352",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-01T13:19:46.655162Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-01T13:20:09.432Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-g344-hcph-8vgg"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:pypi/picklescan",
"product": "picklescan",
"vendor": "picklescan",
"versions": [
{
"lessThan": "0.0.29",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "0.0.29",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*",
"versionEndExcluding": "0.0.29",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "FredericDT"
}
],
"datePublic": "2025-08-26T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "picklescan before 0.0.29 fails to detect the built-in Python trace.Trace.runctx function when used in pickle file reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files with trace.Trace.runctx payloads that bypass picklescan detection and execute code upon pickle.load() invocation."
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 7.6,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-06-30T22:08:17.415Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GitHub Security Advisory (GHSA-g344-hcph-8vgg)",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-g344-hcph-8vgg"
},
{
"name": "VulnCheck Advisory: picklescan - Remote Code Execution via Undetected trace.Trace.runctx in Pickle Files",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/picklescan-remote-code-execution-via-undetected-trace-trace-runctx-in-pickle-files"
}
],
"title": "picklescan - Remote Code Execution via Undetected trace.Trace.runctx in Pickle Files",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2025-71352",
"datePublished": "2026-06-30T22:08:17.415Z",
"dateReserved": "2026-06-20T12:55:02.882Z",
"dateUpdated": "2026-07-01T13:20:09.432Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-71322 (GCVE-0-2025-71322)
Vulnerability from cvelistv5 – Published: 2026-06-17 15:04 – Updated: 2026-06-18 15:19
VLAI
EPSS
VEX
Title
PickleScan - Unsafe Globals Check Bypass via pty.spawn Function
Summary
PickleScan before 0.0.33 fails to include the pty.spawn function in its unsafe globals list, allowing attackers to bypass security checks. Malicious actors can craft pickle payloads using pty.spawn to achieve arbitrary code execution when files are processed by PickleScan.
Severity
SSVC
Exploitation: none
Automatable: no
Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-06-18 15:17 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
2 references
| URL | Tags |
|---|---|
| https://github.com/mmaitre314/picklescan/security… | vendor-advisory |
| https://www.vulncheck.com/advisories/picklescan-u… | third-party-advisory |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| PickleScan | PickleScan |
Affected:
0 , < 0.0.33
(semver)
Unaffected: 0.0.33 (semver) cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:* |
Date Public
2025-12-26 00:00
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-71322",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-06-18T15:17:59.576526Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-06-18T15:19:25.962Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-hgrh-qx5j-jfwx"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageURL": "pkg:pypi/picklescan",
"product": "PickleScan",
"vendor": "PickleScan",
"versions": [
{
"lessThan": "0.0.33",
"status": "affected",
"version": "0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "0.0.33",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:mmaitre314:picklescan:*:*:*:*:*:*:*:*",
"versionEndExcluding": "0.0.33",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "yarienkiva"
}
],
"datePublic": "2025-12-26T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "PickleScan before 0.0.33 fails to include the pty.spawn function in its unsafe globals list, allowing attackers to bypass security checks. Malicious actors can craft pickle payloads using pty.spawn to achieve arbitrary code execution when files are processed by PickleScan."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "PASSIVE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "HIGH"
},
"format": "CVSS"
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-06-17T15:04:59.421Z",
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck"
},
"references": [
{
"name": "GHSA Advisory GHSA-hgrh-qx5j-jfwx",
"tags": [
"vendor-advisory"
],
"url": "https://github.com/mmaitre314/picklescan/security/advisories/GHSA-hgrh-qx5j-jfwx"
},
{
"name": "VulnCheck Advisory: PickleScan - Unsafe Globals Check Bypass via pty.spawn Function",
"tags": [
"third-party-advisory"
],
"url": "https://www.vulncheck.com/advisories/picklescan-unsafe-globals-check-bypass-via-pty-spawn-function"
}
],
"title": "PickleScan - Unsafe Globals Check Bypass via pty.spawn Function",
"x_generator": {
"engine": "vulncheck-endgame"
}
}
},
"cveMetadata": {
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"cveId": "CVE-2025-71322",
"datePublished": "2026-06-17T15:04:59.421Z",
"dateReserved": "2026-06-08T20:44:31.209Z",
"dateUpdated": "2026-06-18T15:19:25.962Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-69264 (GCVE-0-2025-69264)
Vulnerability from cvelistv5 – Published: 2026-01-07 21:53 – Updated: 2026-09-14 12:04
VLAI
EPSS
VEX
Title
pnpm v10+ Bypass "Dependency lifecycle scripts execution disabled by default"
Summary
pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during pnpm install, circumventing the v10 security feature "Dependency lifecycle scripts execution disabled by default". While pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, git dependencies can still execute prepare, prepublish, and prepack scripts during the fetch phase, enabling remote code execution without user consent or approval. This issue is fixed in version 10.26.0.
Severity
8.8 (High)
SSVC
Exploitation: poc
Automatable: no
Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-01-09 04:55 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
5 references
| URL | Tags |
|---|---|
| https://github.com/pnpm/pnpm/security/advisories/… | x_refsource_CONFIRM |
| https://github.com/pnpm/pnpm/commit/73cc63504d9bc… | x_refsource_MISC |
| https://access.redhat.com/security/cve/CVE-2025-69264 | vdb-entryx_refsource_REDHAT |
| https://bugzilla.redhat.com/show_bug.cgi?id=2427709 | issue-trackingx_refsource_REDHAT |
| https://security.access.redhat.com/data/csaf/v2/v… | x_sadp-csaf-vex |
Impacted products
3 products
| Vendor | Product | Version | |
|---|---|---|---|
| pnpm | pnpm |
Affected:
> 10.0.0, < 10.26.0
|
|
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 |
cpe:/a:redhat:jboss_enterprise_application_platform:8
|
|
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack |
cpe:/a:redhat:jbosseapxp
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-69264",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-01-09T04:55:29.582483Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-02-26T15:04:55.476Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"affected": [
{
"collectionURL": "https://access.redhat.com/downloads/content/package-browser/",
"cpes": [
"cpe:/a:redhat:jboss_enterprise_application_platform:8"
],
"defaultStatus": "unaffected",
"packageName": "org.keycloak-keycloak-parent",
"product": "Red Hat JBoss Enterprise Application Platform 8",
"vendor": "Red Hat"
},
{
"collectionURL": "https://access.redhat.com/downloads/content/package-browser/",
"cpes": [
"cpe:/a:redhat:jbosseapxp"
],
"defaultStatus": "unaffected",
"packageName": "org.keycloak-keycloak-parent",
"product": "Red Hat JBoss Enterprise Application Platform Expansion Pack",
"vendor": "Red Hat"
}
],
"datePublic": "2026-01-07T21:53:09.806Z",
"descriptions": [
{
"lang": "en",
"value": "A code execution vector has been discovered in pnpm. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during pnpm install, circumventing the v10 security feature \"Dependency lifecycle scripts execution disabled by default\". While pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, git dependencies can still execute prepare, prepublish, and prepack scripts during the fetch phase, enabling remote code execution without user consent or approval."
}
],
"metrics": [
{
"other": {
"content": {
"namespace": "https://access.redhat.com/security/updates/classification/",
"value": "Important"
},
"type": "Red Hat severity rating"
}
},
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS"
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-09-14T12:04:32.632Z",
"orgId": "0b0ca135-0b70-47e7-9f44-1890c2a1c46c",
"shortName": "redhat-SADP"
},
"references": [
{
"tags": [
"vdb-entry",
"x_refsource_REDHAT"
],
"url": "https://access.redhat.com/security/cve/CVE-2025-69264"
},
{
"name": "RHBZ#2427709",
"tags": [
"issue-tracking",
"x_refsource_REDHAT"
],
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2427709"
},
{
"tags": [
"x_sadp-csaf-vex"
],
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-69264.json"
}
],
"timeline": [
{
"lang": "en",
"time": "2026-01-07T22:02:18.162Z",
"value": "Reported to Red Hat."
},
{
"lang": "en",
"time": "2026-01-07T21:53:09.806Z",
"value": "Made public."
}
],
"title": "pnpm: pnpm code execution",
"x_adpType": "supplier",
"x_generator": {
"engine": "sadp-cli 1.0.0"
}
}
],
"cna": {
"affected": [
{
"product": "pnpm",
"vendor": "pnpm",
"versions": [
{
"status": "affected",
"version": "\u003e 10.0.0, \u003c 10.26.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "pnpm is a package manager. Versions 10.0.0 through 10.25 allow git-hosted dependencies to execute arbitrary code during pnpm install, circumventing the v10 security feature \"Dependency lifecycle scripts execution disabled by default\". While pnpm v10 blocks postinstall scripts via the onlyBuiltDependencies mechanism, git dependencies can still execute prepare, prepublish, and prepack scripts during the fetch phase, enabling remote code execution without user consent or approval. This issue is fixed in version 10.26.0."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "CWE-693: Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-01-07T21:53:09.806Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/pnpm/pnpm/security/advisories/GHSA-379q-355j-w6rj",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/pnpm/pnpm/security/advisories/GHSA-379q-355j-w6rj"
},
{
"name": "https://github.com/pnpm/pnpm/commit/73cc63504d9bc360c43e4b2feb9080677f03c5b5",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/pnpm/pnpm/commit/73cc63504d9bc360c43e4b2feb9080677f03c5b5"
}
],
"source": {
"advisory": "GHSA-379q-355j-w6rj",
"discovery": "UNKNOWN"
},
"title": "pnpm v10+ Bypass \"Dependency lifecycle scripts execution disabled by default\""
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2025-69264",
"datePublished": "2026-01-07T21:53:09.806Z",
"dateReserved": "2025-12-31T01:11:50.649Z",
"dateUpdated": "2026-09-14T12:04:32.632Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-68668 (GCVE-0-2025-68668)
Vulnerability from cvelistv5 – Published: 2025-12-26 21:49 – Updated: 2026-01-05 16:59
VLAI
EPSS
VEX
Title
n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node
Summary
n8n is an open source workflow automation platform. From version 1.0.0 to before 2.0.0, a sandbox bypass vulnerability exists in the Python Code Node that uses Pyodide. An authenticated user with permission to create or modify workflows can exploit this vulnerability to execute arbitrary commands on the host system running n8n, using the same privileges as the n8n process. This issue has been patched in version 2.0.0. Workarounds for this issue involve disabling the Code Node by setting the environment variable NODES_EXCLUDE: "[\"n8n-nodes-base.code\"]", disabling Python support in the Code node by setting the environment variable N8N_PYTHON_ENABLED=false, which was introduced in n8n version 1.104.0, and configuring n8n to use the task runner based Python sandbox via the N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER environment variables.
Severity
9.9 (Critical)
SSVC
Exploitation: none
Automatable: no
Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-12-26 21:54 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
2 references
| URL | Tags |
|---|---|
| https://github.com/n8n-io/n8n/security/advisories… | x_refsource_CONFIRM |
| https://www.smartkeyss.com/post/cve-2025-68668-br… |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-68668",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-12-26T21:54:21.742607Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-12-26T21:59:34.256Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2026-01-05T16:59:41.342Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "https://www.smartkeyss.com/post/cve-2025-68668-breaking-out-of-the-python-sandbox-in-n8n"
}
],
"title": "CVE Program Container",
"x_generator": {
"engine": "ADPogram 0.0.1"
}
}
],
"cna": {
"affected": [
{
"product": "n8n",
"vendor": "n8n-io",
"versions": [
{
"status": "affected",
"version": "\u003e= 1.0.0, \u003c 2.0.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "n8n is an open source workflow automation platform. From version 1.0.0 to before 2.0.0, a sandbox bypass vulnerability exists in the Python Code Node that uses Pyodide. An authenticated user with permission to create or modify workflows can exploit this vulnerability to execute arbitrary commands on the host system running n8n, using the same privileges as the n8n process. This issue has been patched in version 2.0.0. Workarounds for this issue involve disabling the Code Node by setting the environment variable NODES_EXCLUDE: \"[\\\"n8n-nodes-base.code\\\"]\", disabling Python support in the Code node by setting the environment variable N8N_PYTHON_ENABLED=false, which was introduced in n8n version 1.104.0, and configuring n8n to use the task runner based Python sandbox via the N8N_RUNNERS_ENABLED and N8N_NATIVE_PYTHON_RUNNER environment variables."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 9.9,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "CWE-693: Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-12-26T21:49:20.695Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/n8n-io/n8n/security/advisories/GHSA-62r4-hw23-cc8v",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/n8n-io/n8n/security/advisories/GHSA-62r4-hw23-cc8v"
}
],
"source": {
"advisory": "GHSA-62r4-hw23-cc8v",
"discovery": "UNKNOWN"
},
"title": "n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2025-68668",
"datePublished": "2025-12-26T21:49:20.695Z",
"dateReserved": "2025-12-22T23:37:00.930Z",
"dateUpdated": "2026-01-05T16:59:41.342Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-67485 (GCVE-0-2025-67485)
Vulnerability from cvelistv5 – Published: 2025-12-10 00:08 – Updated: 2025-12-10 15:36
VLAI
EPSS
VEX
Title
HTTP/HTTPS Traffic Interception Bypass in mad-proxy
Summary
mad-proxy is a Python-based HTTP/HTTPS proxy server for detection and blocking of malicious web activity using custom security policies. Versions 0.3 and below allow attackers to bypass HTTP/HTTPS traffic interception rules, potentially exposing sensitive traffic. This issue does not have a fix at the time of publication.
Severity
5.3 (Medium)
SSVC
Exploitation: none
Automatable: yes
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-12-10 15:36 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
1 reference
| URL | Tags |
|---|---|
| https://github.com/machphy/mad-proxy/security/adv… | x_refsource_CONFIRM |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-67485",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-12-10T15:36:17.171564Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-12-10T15:36:44.424Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "mad-proxy",
"vendor": "machphy",
"versions": [
{
"status": "affected",
"version": "\u003c= 0.3"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "mad-proxy is a Python-based HTTP/HTTPS proxy server for detection and blocking of malicious web activity using custom security policies. Versions 0.3 and below allow attackers to bypass HTTP/HTTPS traffic interception rules, potentially exposing sensitive traffic. This issue does not have a fix at the time of publication."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "CWE-693: Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-12-10T00:08:39.475Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/machphy/mad-proxy/security/advisories/GHSA-wx63-35hw-2482",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/machphy/mad-proxy/security/advisories/GHSA-wx63-35hw-2482"
}
],
"source": {
"advisory": "GHSA-wx63-35hw-2482",
"discovery": "UNKNOWN"
},
"title": "HTTP/HTTPS Traffic Interception Bypass in mad-proxy"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2025-67485",
"datePublished": "2025-12-10T00:08:39.475Z",
"dateReserved": "2025-12-08T18:02:08.846Z",
"dateUpdated": "2025-12-10T15:36:44.424Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-67460 (GCVE-0-2025-67460)
Vulnerability from cvelistv5 – Published: 2025-12-10 20:37 – Updated: 2026-02-26 16:21
VLAI
EPSS
VEX
Title
Zoom Rooms for Windows - Software Downgrade Protection Mechanism Failure
Summary
Protection Mechanism Failure of Software Downgrade in Zoom Rooms for Windows before 6.6.0 may allow an unauthenticated user to conduct an escalation of privilege via local access.
Severity
7.8 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-12-12 04:55 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
1 reference
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| Zoom Communications Inc. | Zoom Rooms |
Affected:
0 , < 6.6.0
(custom)
|
Date Public
2025-12-09 13:00
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-67460",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-12-12T04:55:50.283551Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-02-26T16:21:05.280Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"platforms": [
"Windows"
],
"product": "Zoom Rooms",
"vendor": "Zoom Communications Inc.",
"versions": [
{
"lessThan": "6.6.0",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"datePublic": "2025-12-09T13:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cspan style=\"background-color: rgb(247, 247, 248);\"\u003eProtection Mechanism Failure of Software Downgrade in Zoom Rooms for Windows before 6.6.0 may allow an unauthenticated user to conduct an escalation of privilege via local access.\u003c/span\u003e\u003cbr\u003e"
}
],
"value": "Protection Mechanism Failure of Software Downgrade in Zoom Rooms for Windows before 6.6.0 may allow an unauthenticated user to conduct an escalation of privilege via local access."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "CWE-693: Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-12-10T20:37:03.144Z",
"orgId": "99b9af0d-a833-4a5d-9e2f-8b1324f35351",
"shortName": "Zoom"
},
"references": [
{
"url": "https://www.zoom.com/en/trust/security-bulletin/zsb-25050"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Zoom Rooms for Windows - Software Downgrade Protection Mechanism Failure",
"x_generator": {
"engine": "Vulnogram 0.5.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "99b9af0d-a833-4a5d-9e2f-8b1324f35351",
"assignerShortName": "Zoom",
"cveId": "CVE-2025-67460",
"datePublished": "2025-12-10T20:37:03.144Z",
"dateReserved": "2025-12-08T13:59:49.274Z",
"dateUpdated": "2026-02-26T16:21:05.280Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-66479 (GCVE-0-2025-66479)
Vulnerability from cvelistv5 – Published: 2025-12-04 20:57 – Updated: 2025-12-05 17:04
VLAI
EPSS
VEX
Title
Anthropic Sandbox Runtime Incorrectly Implemented Network Sandboxing
Summary
Anthropic Sandbox Runtime is a lightweight sandboxing tool for enforcing filesystem and network restrictions on arbitrary processes at the OS level, without requiring a container. Prior to 0.0.16, due to a bug in sandboxing logic, sandbox-runtime did not properly enforce a network sandbox if the sandbox policy did not configure any allowed domains. This could allow sandboxed code to make network requests outside of the sandbox. A patch for this was released in v0.0.16.
Severity
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-12-05 17:04 UTC
CWE
- CWE-693 - Protection Mechanism Failure
Assigner
References
2 references
| URL | Tags |
|---|---|
| https://github.com/anthropic-experimental/sandbox… | x_refsource_CONFIRM |
| https://github.com/anthropic-experimental/sandbox… | x_refsource_MISC |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| anthropic-experimental | sandbox-runtime |
Affected:
< 0.0.16
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-66479",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-12-05T17:04:23.072749Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-12-05T17:04:34.471Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "sandbox-runtime",
"vendor": "anthropic-experimental",
"versions": [
{
"status": "affected",
"version": "\u003c 0.0.16"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Anthropic Sandbox Runtime is a lightweight sandboxing tool for enforcing filesystem and network restrictions on arbitrary processes at the OS level, without requiring a container. Prior to 0.0.16, due to a bug in sandboxing logic, sandbox-runtime did not properly enforce a network sandbox if the sandbox policy did not configure any allowed domains. This could allow sandboxed code to make network requests outside of the sandbox. A patch for this was released in v0.0.16."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "LOCAL",
"baseScore": 1.8,
"baseSeverity": "LOW",
"privilegesRequired": "HIGH",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "CWE-693: Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-12-04T20:57:20.631Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/anthropic-experimental/sandbox-runtime/security/advisories/GHSA-9gqj-5w7c-vx47",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/anthropic-experimental/sandbox-runtime/security/advisories/GHSA-9gqj-5w7c-vx47"
},
{
"name": "https://github.com/anthropic-experimental/sandbox-runtime/commit/bea2930cc1db9c73a1b15acf6dc19c5261aec1f3",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/anthropic-experimental/sandbox-runtime/commit/bea2930cc1db9c73a1b15acf6dc19c5261aec1f3"
}
],
"source": {
"advisory": "GHSA-9gqj-5w7c-vx47",
"discovery": "UNKNOWN"
},
"title": "Anthropic Sandbox Runtime Incorrectly Implemented Network Sandboxing"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2025-66479",
"datePublished": "2025-12-04T20:57:20.631Z",
"dateReserved": "2025-12-02T17:09:52.016Z",
"dateUpdated": "2025-12-05T17:04:34.471Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2025-66204 (GCVE-0-2025-66204)
Vulnerability from cvelistv5 – Published: 2025-12-08 23:50 – Updated: 2025-12-09 16:03
VLAI
EPSS
VEX
Title
WBCE CMS allows brute-force protection bypass using X-Forwarded-For header
Summary
WBCE CMS is a content management system. Version 1.6.4 contains a brute-force protection bypass where an attacker can indefinitely reset the counter by modifying `X-Forwarded-For` on each request, gaining unlimited password guessing attempts, effectively bypassing all brute-force protection. The application fully trusts the `X-Forwarded-For` header without validating it or restricting its usage. This issue is fixed in version 1.6.5.
Severity
SSVC
Exploitation: poc
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2025-12-09 14:18 UTC
CWE
Assigner
References
3 references
| URL | Tags |
|---|---|
| https://github.com/WBCE/WBCE_CMS/security/advisor… | x_refsource_CONFIRM |
| https://github.com/WBCE/WBCE_CMS/commit/3765baddf… | x_refsource_MISC |
| https://github.com/WBCE/WBCE_CMS/releases/tag/1.6.5 | x_refsource_MISC |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2025-66204",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-12-09T14:18:12.951947Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2025-12-09T16:03:59.128Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/WBCE/WBCE_CMS/security/advisories/GHSA-f676-f375-m7mw"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "WBCE_CMS",
"vendor": "WBCE",
"versions": [
{
"status": "affected",
"version": "\u003e= 1.6.4, \u003c 1.6.5"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "WBCE CMS is a content management system. Version 1.6.4 contains a brute-force protection bypass where an attacker can indefinitely reset the counter by modifying `X-Forwarded-For` on each request, gaining unlimited password guessing attempts, effectively bypassing all brute-force protection. The application fully trusts the `X-Forwarded-For` header without validating it or restricting its usage. This issue is fixed in version 1.6.5."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "HIGH",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.3,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-307",
"description": "CWE-307: Improper Restriction of Excessive Authentication Attempts",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-693",
"description": "CWE-693: Protection Mechanism Failure",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2025-12-08T23:50:58.647Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/WBCE/WBCE_CMS/security/advisories/GHSA-f676-f375-m7mw",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/WBCE/WBCE_CMS/security/advisories/GHSA-f676-f375-m7mw"
},
{
"name": "https://github.com/WBCE/WBCE_CMS/commit/3765baddf27f31bbbea9c0228c452268621b25e5",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/WBCE/WBCE_CMS/commit/3765baddf27f31bbbea9c0228c452268621b25e5"
},
{
"name": "https://github.com/WBCE/WBCE_CMS/releases/tag/1.6.5",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/WBCE/WBCE_CMS/releases/tag/1.6.5"
}
],
"source": {
"advisory": "GHSA-f676-f375-m7mw",
"discovery": "UNKNOWN"
},
"title": "WBCE CMS allows brute-force protection bypass using X-Forwarded-For header"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2025-66204",
"datePublished": "2025-12-08T23:50:58.647Z",
"dateReserved": "2025-11-24T23:01:29.677Z",
"dateUpdated": "2025-12-09T16:03:59.128Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
No mitigation information available for this CWE.
CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
CAPEC-107: Cross Site Tracing
Cross Site Tracing (XST) enables an adversary to steal the victim's session cookie and possibly other authentication credentials transmitted in the header of the HTTP request when the victim's browser communicates to a destination system's web server.
CAPEC-127: Directory Indexing
An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
CAPEC-17: Using Malicious Files
An attack of this type exploits a system's configuration that allows an adversary to either directly access an executable file, for example through shell access; or in a possible worst case allows an adversary to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
CAPEC-20: Encryption Brute Forcing
An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.
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-237: Escaping a Sandbox by Calling Code in Another Language
The attacker may submit malicious code of another language to obtain access to privileges that were not intentionally exposed by the sandbox, thus escaping the sandbox. For instance, Java code cannot perform unsafe operations, such as modifying arbitrary memory locations, due to restrictions placed on it by the Byte code Verifier and the JVM. If allowed, Java code can call directly into native C code, which may perform unsafe operations, such as call system calls and modify arbitrary memory locations on their behalf. To provide isolation, Java does not grant untrusted code with unmediated access to native C code. Instead, the sandboxed code is typically allowed to call some subset of the pre-existing native code that is part of standard libraries.
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-477: Signature Spoofing by Mixing Signed and Unsigned Content
An attacker exploits the underlying complexity of a data structure that allows for both signed and unsigned content, to cause unsigned data to be processed as though it were signed data.
CAPEC-480: Escaping Virtualization
An adversary gains access to an application, service, or device with the privileges of an authorized or privileged user by escaping the confines of a virtualized environment. The adversary is then able to access resources or execute unauthorized code within the host environment, generally with the privileges of the user running the virtualized process. Successfully executing an attack of this type is often the first step in executing more complex attacks.
CAPEC-51: Poison Web Service Registry
SOA and Web Services often use a registry to perform look up, get schema information, and metadata about services. A poisoned registry can redirect (think phishing for servers) the service requester to a malicious service provider, provide incorrect information in schema or metadata, and delete information about service provider interfaces.
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-59: Session Credential Falsification through Prediction
This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
CAPEC-65: Sniff Application Code
An adversary passively sniffs network communications and captures application code bound for an authorized client. Once obtained, they can use it as-is, or through reverse-engineering glean sensitive information or exploit the trust relationship between the client and server. Such code may belong to a dynamic update to the client, a patch being applied to a client component or any such interaction where the client is authorized to communicate with the server.
CAPEC-668: Key Negotiation of Bluetooth Attack (KNOB)
An adversary can exploit a flaw in Bluetooth key negotiation allowing them to decrypt information sent between two devices communicating via Bluetooth. The adversary uses an Adversary in the Middle setup to modify packets sent between the two devices during the authentication process, specifically the entropy bits. Knowledge of the number of entropy bits will allow the attacker to easily decrypt information passing over the line of communication.
CAPEC-74: Manipulating State
The adversary modifies state information maintained by the target software or causes a state transition in hardware. If successful, the target will use this tainted state and execute in an unintended manner.
State management is an important function within a software application. User state maintained by the application can include usernames, payment information, browsing history as well as application-specific contents such as items in a shopping cart. Manipulating user state can be employed by an adversary to elevate privilege, conduct fraudulent transactions or otherwise modify the flow of the application to derive certain benefits.
If there is a hardware logic error in a finite state machine, the adversary can use this to put the system in an undefined state which could cause a denial of service or exposure of secure data.
CAPEC-87: Forceful Browsing
An attacker employs forceful browsing (direct URL entry) to access portions of a website that are otherwise unreachable. Usually, a front controller or similar design pattern is employed to protect access to portions of a web application. Forceful browsing enables an attacker to access information, perform privileged operations and otherwise reach sections of the web application that have been improperly protected.