CWE-116
Allowed-with-ReviewImproper Encoding or Escaping of Output
Abstraction: Class · Status: Draft
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
612 vulnerabilities reference this CWE, most recent first.
GHSA-5C4W-8HHH-3C3H
Vulnerability from github – Published: 2024-10-31 00:30 – Updated: 2025-01-10 16:03A vulnerability was identified in Consul and Consul Enterprise ("Consul") such that using Headers in L7 traffic intentions could bypass HTTP header based access rules.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/hashicorp/consul"
},
"ranges": [
{
"events": [
{
"introduced": "1.9.0"
},
{
"fixed": "1.20.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2024-10006"
],
"database_specific": {
"cwe_ids": [
"CWE-116",
"CWE-644"
],
"github_reviewed": true,
"github_reviewed_at": "2024-10-31T14:49:31Z",
"nvd_published_at": "2024-10-30T22:15:03Z",
"severity": "MODERATE"
},
"details": "A vulnerability was identified in Consul and Consul Enterprise (\"Consul\") such that using Headers in L7 traffic intentions could bypass HTTP header based access rules.",
"id": "GHSA-5c4w-8hhh-3c3h",
"modified": "2025-01-10T16:03:56Z",
"published": "2024-10-31T00:30:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-10006"
},
{
"type": "WEB",
"url": "https://github.com/hashicorp/consul/pull/21816"
},
{
"type": "WEB",
"url": "https://github.com/hashicorp/consul/commit/d9206fc7e284a9244af4d62f8653a63ca30bd00c"
},
{
"type": "WEB",
"url": "https://discuss.hashicorp.com/t/hcsec-2024-23-consul-l7-intentions-vulnerable-to-headers-bypass"
},
{
"type": "PACKAGE",
"url": "https://github.com/hashicorp/consul"
},
{
"type": "WEB",
"url": "https://security.netapp.com/advisory/ntap-20250110-0005"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L",
"type": "CVSS_V4"
}
],
"summary": "Hashicorp Consul Improper Neutralization of HTTP Headers for Scripting Syntax vulnerability"
}
GHSA-5F64-7VFC-RCX6
Vulnerability from github – Published: 2026-05-14 18:27 – Updated: 2026-06-12 22:02Summary
A stored cross-site scripting vulnerability was identified in the image widget functionality. A user with the Editor role can configure an image widget link to use a javascript: URL payload.
Because editors have permission to publish pages, the malicious widget can be published to the live site. When another user, including an administrator or public visitor, clicks the affected image/link, arbitrary JavaScript executes in the victim’s browser.
Affected Version
ApostropheCMS (tested on version: v4.29.0)
Steps to Reproduce
Precondition Ensure at least one image exists in the media library.
If the media library is empty: - Log in as an Editor. - Open the media library. - Upload any JPG or PNG image. - Set any title, for example Probe image. - Publish the image and close the media manager.
Exploitation Steps
- Log in as an Editor.
- Open the home page.
- Enable edit mode for the page.
- In the main content area, click Add content.
- Select the Image widget.
- Choose any existing image from the image picker and save/select it.
- Open the image widget settings.
- Locate the Link to field and change it to URL.
-
In the URL field, enter:
javascript:alert(document.domain) -
Save the image and click on Update.
- As another user, such as an administrator or guest, open the published page and click the linked image.
- Observe that the JavaScript payload executes.
Note: This attack can also be performed by a Contributor. However, because contributors cannot publish content directly, the malicious image widget remains in the draft version and is only visible to users with access to review drafts, such as administrators or editors.
If an administrator reviews and approves/publishes the affected draft, the stored XSS becomes part of the live page and can then affect all users who interact with the malicious image link.
Impact
Successful exploitation allows an Editor to store a JavaScript payload in published page content. When a victim clicks the affected image link, the payload executes in the victim’s browser.
This may allow an attacker to:
- perform actions in the context of an authenticated administrator
- access sensitive information available in the CMS interface
- modify page content or configuration
- conduct phishing attacks within the trusted site
- compromise visitors who interact with the published image link
Recommendation
Validate and sanitize all user-supplied URLs used in widget link fields.
Specifically:
- Reject dangerous URL schemes such as javascript:, data:, and other executable schemes.
- Allow only safe protocols such as http:, https:, mailto:, and relative URLs where appropriate.
- Normalize and validate URLs server-side before storage.
- Encode rendered URLs safely in templates.
- Consider applying a strict Content Security Policy to reduce the impact of XSS.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "apostrophe"
},
"versions": [
"4.29.0"
]
}
],
"aliases": [
"CVE-2026-45011"
],
"database_specific": {
"cwe_ids": [
"CWE-116",
"CWE-79"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-14T18:27:56Z",
"nvd_published_at": "2026-06-12T21:16:22Z",
"severity": "HIGH"
},
"details": "### Summary\nA stored cross-site scripting vulnerability was identified in the image widget functionality. A user with the Editor role can configure an image widget link to use a javascript: URL payload.\n\nBecause editors have permission to publish pages, the malicious widget can be published to the live site. When another user, including an administrator or public visitor, clicks the affected image/link, arbitrary JavaScript executes in the victim\u2019s browser.\n\n### Affected Version\nApostropheCMS (tested on version: v4.29.0)\n\n### Steps to Reproduce\n**Precondition**\nEnsure at least one image exists in the media library.\n\nIf the media library is empty:\n- Log in as an Editor.\n- Open the media library.\n- Upload any JPG or PNG image.\n- Set any title, for example Probe image.\n- Publish the image and close the media manager.\n\n**Exploitation Steps**\n\n- Log in as an Editor.\n- Open the home page.\n- Enable edit mode for the page.\n- In the main content area, click Add content.\n- Select the Image widget.\n- Choose any existing image from the image picker and save/select it.\n- Open the image widget settings.\n- Locate the Link to field and change it to URL.\n- In the URL field, enter: ```javascript:alert(document.domain)```\n\u003cimg width=\"1249\" height=\"979\" alt=\"image\" src=\"https://github.com/user-attachments/assets/c7f77177-1711-461d-b9bd-14292a6996d5\" /\u003e\n\n- Save the image and click on Update.\n- As another user, such as an administrator or guest, open the published page and click the linked image.\n- Observe that the JavaScript payload executes.\n\u003cimg width=\"1267\" height=\"1034\" alt=\"image\" src=\"https://github.com/user-attachments/assets/a80484b4-873a-47c1-8682-84626523008a\" /\u003e\n\n**Note**: This attack can also be performed by a Contributor. However, because contributors cannot publish content directly, the malicious image widget remains in the draft version and is only visible to users with access to review drafts, such as administrators or editors.\n\nIf an administrator reviews and approves/publishes the affected draft, the stored XSS becomes part of the live page and can then affect all users who interact with the malicious image link.\n\n### Impact\nSuccessful exploitation allows an Editor to store a JavaScript payload in published page content. When a victim clicks the affected image link, the payload executes in the victim\u2019s browser.\n\nThis may allow an attacker to:\n\n- perform actions in the context of an authenticated administrator\n- access sensitive information available in the CMS interface\n- modify page content or configuration\n- conduct phishing attacks within the trusted site\n- compromise visitors who interact with the published image link\n\n### Recommendation\n\nValidate and sanitize all user-supplied URLs used in widget link fields.\n\nSpecifically:\n\n- Reject dangerous URL schemes such as javascript:, data:, and other executable schemes.\n- Allow only safe protocols such as http:, https:, mailto:, and relative URLs where appropriate.\n- Normalize and validate URLs server-side before storage.\n- Encode rendered URLs safely in templates.\n- Consider applying a strict Content Security Policy to reduce the impact of XSS.",
"id": "GHSA-5f64-7vfc-rcx6",
"modified": "2026-06-12T22:02:05Z",
"published": "2026-05-14T18:27:56Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-5f64-7vfc-rcx6"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-45011"
},
{
"type": "PACKAGE",
"url": "https://github.com/apostrophecms/apostrophe"
},
{
"type": "WEB",
"url": "https://github.com/apostrophecms/apostrophe/releases/tag/apostrophe%404.29.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
],
"summary": "Apostrophe has stored XSS via javascript: URL in Image Widget Link"
}
GHSA-5F87-FVJM-HRF5
Vulnerability from github – Published: 2022-04-08 00:00 – Updated: 2022-04-15 00:01Host Header injection in password Reset in GitHub repository livehelperchat/livehelperchat prior to 3.97.
{
"affected": [],
"aliases": [
"CVE-2022-0935"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-04-07T19:15:00Z",
"severity": "HIGH"
},
"details": "Host Header injection in password Reset in GitHub repository livehelperchat/livehelperchat prior to 3.97.",
"id": "GHSA-5f87-fvjm-hrf5",
"modified": "2022-04-15T00:01:02Z",
"published": "2022-04-08T00:00:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-0935"
},
{
"type": "WEB",
"url": "https://github.com/livehelperchat/livehelperchat/commit/ce96791cb4c7420266b668fc234c211914259ba7"
},
{
"type": "WEB",
"url": "https://huntr.dev/bounties/a7e40fdf-a333-4a50-8a53-d11b16ce3ec2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-5FG8-2547-MR8Q
Vulnerability from github – Published: 2021-08-03 16:57 – Updated: 2024-02-22 19:03Impact
xmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.
Patches
Update to one of the fixed versions of @xmldom/xmldom (>=0.7.0)
See issue #271 for the status of publishing xmldom to npm or join #270 for Q&A/discussion until it's resolved.
Workarounds
Downstream applications can validate the input and reject the maliciously crafted documents.
References
Similar to this one reported on the Go standard library:
- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/
- https://mattermost.com/blog/securing-xml-implementations-across-the-web/
For more information
If you have any questions or comments about this advisory:
- Open an issue in
xmldom/xmldom - Email us: send an email to all addresses that are shown by
npm owner ls @xmldom/xmldom
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "xmldom"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.6.0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "@xmldom/xmldom"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.7.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-32796"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": true,
"github_reviewed_at": "2021-08-02T23:21:11Z",
"nvd_published_at": "2021-07-27T22:15:00Z",
"severity": "MODERATE"
},
"details": "### Impact\nxmldom versions 0.6.0 and older do not correctly escape special characters when serializing elements removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.\n\n### Patches\nUpdate to one of the fixed versions of `@xmldom/xmldom` (`\u003e=0.7.0`)\n\nSee issue #271 for the status of publishing `xmldom` to npm or join #270 for Q\u0026A/discussion until it\u0027s resolved.\n\n### Workarounds\n\nDownstream applications can validate the input and reject the maliciously crafted documents.\n\n### References\n\nSimilar to this one reported on the Go standard library:\n\n- https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities/\n- https://mattermost.com/blog/securing-xml-implementations-across-the-web/\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\n* Open an issue in [`xmldom/xmldom`](https://github.com/xmldom/xmldom)\n* Email us: send an email to **all** addresses that are shown by `npm owner ls @xmldom/xmldom`\n",
"id": "GHSA-5fg8-2547-mr8q",
"modified": "2024-02-22T19:03:28Z",
"published": "2021-08-03T16:57:05Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/security/advisories/GHSA-5fg8-2547-mr8q"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-32796"
},
{
"type": "WEB",
"url": "https://github.com/xmldom/xmldom/commit/7b4b743917a892d407356e055b296dcd6d107e8b"
},
{
"type": "PACKAGE",
"url": "https://github.com/xmldom/xmldom"
},
{
"type": "WEB",
"url": "https://mattermost.com/blog/coordinated-disclosure-go-xml-vulnerabilities"
},
{
"type": "WEB",
"url": "https://mattermost.com/blog/securing-xml-implementations-across-the-web"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/package/@xmldom/xmldom"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Misinterpretation of malicious XML input"
}
GHSA-5FP8-C45M-256P
Vulnerability from github – Published: 2022-05-24 19:20 – Updated: 2024-11-18 16:26Improper output neutralization for Logs. A specific Apache Superset HTTP endpoint allowed for an authenticated user to forge log entries or inject malicious content into logs.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.3.1"
},
"package": {
"ecosystem": "PyPI",
"name": "apache-superset"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.3.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2021-42250"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": true,
"github_reviewed_at": "2022-06-21T20:08:57Z",
"nvd_published_at": "2021-11-17T15:15:00Z",
"severity": "HIGH"
},
"details": "Improper output neutralization for Logs. A specific Apache Superset HTTP endpoint allowed for an authenticated user to forge log entries or inject malicious content into logs.",
"id": "GHSA-5fp8-c45m-256p",
"modified": "2024-11-18T16:26:26Z",
"published": "2022-05-24T19:20:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-42250"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-5fp8-c45m-256p"
},
{
"type": "WEB",
"url": "https://github.com/apache/superset"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/apache-superset/PYSEC-2021-435.yaml"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread/53lkszw6d3tybp5t99nvgcj538b9trw9"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2021/11/17/2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Improper Encoding or Escaping of Output in Apache Superset"
}
GHSA-5G34-X2RF-M7V6
Vulnerability from github – Published: 2022-12-22 21:30 – Updated: 2025-04-16 15:34SVG's <use> element could have been used to load unexpected content that could have executed script in certain circumstances. While the specification seems to allow this, other browsers do not, and web developers relied on this property for script security so gecko's implementation was aligned with theirs. This vulnerability affects Firefox < 99.
{
"affected": [],
"aliases": [
"CVE-2022-28284"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-12-22T20:15:00Z",
"severity": "HIGH"
},
"details": "SVG\u0027s \u003ccode\u003e\u0026lt;use\u0026gt;\u003c/code\u003e element could have been used to load unexpected content that could have executed script in certain circumstances. While the specification seems to allow this, other browsers do not, and web developers relied on this property for script security so gecko\u0027s implementation was aligned with theirs. This vulnerability affects Firefox \u003c 99.",
"id": "GHSA-5g34-x2rf-m7v6",
"modified": "2025-04-16T15:34:07Z",
"published": "2022-12-22T21:30:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-28284"
},
{
"type": "WEB",
"url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1754522"
},
{
"type": "WEB",
"url": "https://www.mozilla.org/security/advisories/mfsa2022-13"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-5M5X-9J46-H678
Vulnerability from github – Published: 2025-09-09 18:31 – Updated: 2025-09-12 19:05Element Plus Link component (el-link) prior to 2.11.0 implements insufficient input validation for the href attribute, creating a security abstraction gap that obscures URL-based attack vectors. The component passes user-controlled href values directly to underlying anchor elements without protocol validation, URL sanitization, or security headers. This allows attackers to inject malicious URLs using dangerous protocols (javascript:, data:, file:) or redirect users to external malicious sites. While native HTML anchor elements present similar risks, UI component libraries bear additional responsibility for implementing security safeguards and providing clear risk documentation. The vulnerability enables XSS attacks, phishing campaigns, and open redirect exploits affecting applications that use Element Plus Link components with user-controlled or untrusted URL inputs. As of version 2.11.0, Element Plus have clearly documented the risks inherent with the component.
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "element-plus"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "2.11.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-57665"
],
"database_specific": {
"cwe_ids": [
"CWE-116",
"CWE-20"
],
"github_reviewed": true,
"github_reviewed_at": "2025-09-10T20:41:39Z",
"nvd_published_at": "2025-09-09T18:15:36Z",
"severity": "MODERATE"
},
"details": "Element Plus Link component (el-link) prior to 2.11.0 implements insufficient input validation for the href attribute, creating a security abstraction gap that obscures URL-based attack vectors. The component passes user-controlled href values directly to underlying anchor elements without protocol validation, URL sanitization, or security headers. This allows attackers to inject malicious URLs using dangerous protocols (javascript:, data:, file:) or redirect users to external malicious sites. While native HTML anchor elements present similar risks, UI component libraries bear additional responsibility for implementing security safeguards and providing clear risk documentation. The vulnerability enables XSS attacks, phishing campaigns, and open redirect exploits affecting applications that use Element Plus Link components with user-controlled or untrusted URL inputs. As of version 2.11.0, Element Plus have clearly documented the risks inherent with the component.",
"id": "GHSA-5m5x-9j46-h678",
"modified": "2025-09-12T19:05:43Z",
"published": "2025-09-09T18:31:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-57665"
},
{
"type": "WEB",
"url": "https://github.com/element-plus/element-plus/pull/21711"
},
{
"type": "WEB",
"url": "https://github.com/element-plus/element-plus/commit/110d4e1d7e150ccb829771c7319d31ce777d102f"
},
{
"type": "WEB",
"url": "https://element-plus.org/en-US/component/link.html"
},
{
"type": "PACKAGE",
"url": "https://github.com/element-plus/element-plus"
},
{
"type": "WEB",
"url": "https://github.com/element-plus/element-plus/blob/dev/packages/components/link/src/link.vue"
},
{
"type": "WEB",
"url": "https://www.npmjs.com/package/element-plus"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U",
"type": "CVSS_V4"
}
],
"summary": "Element Plus Link component (el-link) implements insufficient input validation for the href attribute"
}
GHSA-5MVP-47XW-3292
Vulnerability from github – Published: 2022-05-24 16:55 – Updated: 2024-04-04 01:53In Counter-Strike: Global Offensive before 8/29/2019, community game servers can display unsafe HTML in a disconnection message.
{
"affected": [],
"aliases": [
"CVE-2019-15944"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-09-05T20:15:00Z",
"severity": "MODERATE"
},
"details": "In Counter-Strike: Global Offensive before 8/29/2019, community game servers can display unsafe HTML in a disconnection message.",
"id": "GHSA-5mvp-47xw-3292",
"modified": "2024-04-04T01:53:30Z",
"published": "2022-05-24T16:55:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-15944"
},
{
"type": "WEB",
"url": "https://blog.counter-strike.net/index.php/2019/08/25353"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-5R6P-P9R6-R326
Vulnerability from github – Published: 2022-05-24 16:51 – Updated: 2022-06-28 22:38Jenkins Configuration as Code Plugin 1.24 and earlier did not escape values resulting in variable interpolation during configuration import when exporting, allowing attackers with permission to change Jenkins system configuration to obtain the values of environment variables.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.24"
},
"package": {
"ecosystem": "Maven",
"name": "io.jenkins:configuration-as-code"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.25"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2019-10362"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": true,
"github_reviewed_at": "2022-06-28T22:38:20Z",
"nvd_published_at": "2019-07-31T13:15:00Z",
"severity": "MODERATE"
},
"details": "Jenkins Configuration as Code Plugin 1.24 and earlier did not escape values resulting in variable interpolation during configuration import when exporting, allowing attackers with permission to change Jenkins system configuration to obtain the values of environment variables.",
"id": "GHSA-5r6p-p9r6-r326",
"modified": "2022-06-28T22:38:20Z",
"published": "2022-05-24T16:51:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-10362"
},
{
"type": "WEB",
"url": "https://github.com/jenkinsci/configuration-as-code-plugin/commit/b48a292112c532ab1447b864c7d30c2cae733ac8"
},
{
"type": "WEB",
"url": "https://jenkins.io/security/advisory/2019-07-31/#SECURITY-1446"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2019/07/31/1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
"type": "CVSS_V3"
}
],
"summary": "Improper Encoding or Escaping of Output in Jenkins Configuration as Code Plugin"
}
GHSA-5V8V-CP6R-MQ7C
Vulnerability from github – Published: 2022-09-25 00:00 – Updated: 2025-06-01 12:30In Kitty before 0.26.2, insufficient validation in the desktop notification escape sequence can lead to arbitrary code execution. The user must display attacker-controlled content in the terminal, then click on a notification popup.
{
"affected": [],
"aliases": [
"CVE-2022-41322"
],
"database_specific": {
"cwe_ids": [
"CWE-116"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-09-23T05:15:00Z",
"severity": "HIGH"
},
"details": "In Kitty before 0.26.2, insufficient validation in the desktop notification escape sequence can lead to arbitrary code execution. The user must display attacker-controlled content in the terminal, then click on a notification popup.",
"id": "GHSA-5v8v-cp6r-mq7c",
"modified": "2025-06-01T12:30:24Z",
"published": "2022-09-25T00:00:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-41322"
},
{
"type": "WEB",
"url": "https://github.com/kovidgoyal/kitty/commit/f05783e64d5fa62e1aed603e8d69aced5e49824f"
},
{
"type": "WEB",
"url": "https://bugs.gentoo.org/868543"
},
{
"type": "WEB",
"url": "https://github.com/kovidgoyal/kitty/compare/v0.26.1...v0.26.2"
},
{
"type": "WEB",
"url": "https://lists.debian.org/debian-lts-announce/2025/06/msg00000.html"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/47RK7MBSVY5BWDUTYMJUFPBAYFSWMTOI"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6RRNAPU33PHEH64P77YL3AJO6CTZGHTX"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/47RK7MBSVY5BWDUTYMJUFPBAYFSWMTOI"
},
{
"type": "WEB",
"url": "https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6RRNAPU33PHEH64P77YL3AJO6CTZGHTX"
},
{
"type": "WEB",
"url": "https://security.gentoo.org/glsa/202209-22"
},
{
"type": "WEB",
"url": "https://sw.kovidgoyal.net/kitty/changelog/#detailed-list-of-changes"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Mitigation MIT-4.3
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error.
- Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.
Mitigation MIT-27
Strategy: Parameterization
- If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
- For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.
Mitigation
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.
Mitigation
In some cases, input validation may be an important strategy when output encoding is not a complete solution. For example, you may be providing the same output that will be processed by multiple consumers that use different encodings or representations. In other cases, you may be required to allow user-supplied input to contain control information, such as limited HTML tags that support formatting in a wiki or bulletin board. When this type of requirement must be met, use an extremely strict allowlist to limit which control sequences can be used. Verify that the resulting syntactic structure is what you expect. Use your normal encoding methods for the remainder of the input.
Mitigation
Use input validation as a defense-in-depth measure to reduce the likelihood of output encoding errors (see CWE-20).
Mitigation
Fully specify which encodings are required by components that will be communicating with each other.
Mitigation
When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.
CAPEC-104: Cross Zone Scripting
An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security.
CAPEC-73: User-Controlled Filename
An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.
CAPEC-81: Web Server Logs Tampering
Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.
CAPEC-85: AJAX Footprinting
This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.