GHSA-6cj3-rc4p-f38f: Neos/neos Cross-Site Scripting Vulnerability

HIGH
Share
CWE-79
Published
Advisory Summary

GHSA-6cj3-rc4p-f38f is a HIGH cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Neos/neos libraries in the Packagist ecosystem. The issue involves cross-site scripting vulnerabilities in neos. Remediation is available by upgrading affected packages to version 1.2.13, 2.0.4.

GHSA-6cj3-rc4p-f38f at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-6cj3-rc4p-f38f
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Neos/neos
Package Ecosystem Packagist
Published Date
Last Updated

How to Fix GHSA-6cj3-rc4p-f38f

To remediate this vulnerability, upgrade all affected Neos/neos dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

neos/neos fixed: 1.2.13 
Upgrade neos/neos to 1.2.13
neos/neos fixed: 2.0.4 
Upgrade neos/neos to 2.0.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for neos/neos

How to Check if You Are Affected

To determine whether your application is affected by GHSA-6cj3-rc4p-f38f, inspect your project dependencies for Neos/neos:

inspect dependencies for neos/neos

Analyze the terminal output to locate any version of Neos/neos in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.13), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Neos/neos, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

It has been discovered that Neos is vulnerable to several XSS attacks. Through these vulnerabilities, an attacker could tamper with page rendering, redirect victims to a fake login page, or capture user credentials (such as cookies). With the potential backdoor upload an attacker could gain access to the server itself, to an extent mainly limited by the server setup. ### Reflected Cross-Site Scripting (SXSS) with authentication A Neos backend user with permission to modify content can insert JavaScript instructions into content elements. The browser will execute the script in "Print" preview mode. A Neos backend user who can modify his profile information ("Title", "First Name", "Last name", "Middle Name", "Other Name") can inject JavaScript instructions in those parameters. Once set up, an administrator who wants to edit this user account will execute the code. Both attack vectors require a valid Neos backend user account. ### Reflected Cross-Site Scripting (RXSS) without authentication A non-persistent XSS using parameters passed during plugin execution is possible. If invalid parameters are passed, an error message may be shown (depending on the context Neos runs in and how the parameters are handled) that contains the unescaped parameter value. Note: Through the HTML content type the inclusion of arbitrary JavaScript is still possible for users with a valid Neos backend account. If you want to prohibit that, disable the nodetype or restrict access. ### Potential backdoor upload Through an issue with the underlying Flow framework (see the related Flow advisory Flow-SA-2015-001) any editor with access to the Media Management module can upload server side script files (when using Neos 2.0.x). If those scripts are executed by the server when accessed through their public URL, anything not blocked through other means is possible (information disclosure, placement of backdoors, data removal, …).

GHSA-6cj3-rc4p-f38f Affected Neos/neos Versions

2 component(s)
Fixed Versions:
1.2.132.0.4
Product / Package Ecosystem Affected Versions Fixed Version
neos/neos
 Packagist
≥ 1.2.0
< 1.2.13
1.2.13
neos/neos
 Packagist
≥ 2.0.0
< 2.0.4
2.0.4

References

Neos/neos Source Repository REPOSITORY
https://github.com/FriendsOfPHP/security-advisories/blob/master/neos/neos/2015-11-23.yaml
Neos/neos Source Repository REPOSITORY
https://github.com/neos/neos
www.neos.io/blog/neos-sa-2015-0... WEB
https://www.neos.io/blog/neos-sa-2015-002.html

Frequently Asked Questions

What is GHSA-6cj3-rc4p-f38f?
GHSA-6cj3-rc4p-f38f is a security vulnerability in Neos/neos involving Cross-site Scripting vulnerabilities in Neos under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Neos/neos versions are affected?
Affected versions include releases prior to 1.2.13, 2.0.4 across affected packages: neos/neos.
What version fixes GHSA-6cj3-rc4p-f38f?
Upgrading to 1.2.13, 2.0.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is neos/neos affected?
Yes, neos/neos is affected in releases prior to 1.2.13, 2.0.4. Upgrade your dependency to 1.2.13, 2.0.4 or later.
What CWE is associated with GHSA-6cj3-rc4p-f38f?
GHSA-6cj3-rc4p-f38f is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check Packagist dependencies for GHSA-6cj3-rc4p-f38f?
Run the dependency tree command: 'inspect dependencies for neos/neos'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6cj3-rc4p-f38f",
  "modified" : "2024-05-17T23:04:02Z",
  "published" : "2024-05-17T23:04:02Z",
  "aliases" : [ ],
  "summary" : "Cross-site Scripting vulnerabilities in Neos",
  "details" : "It has been discovered that Neos is vulnerable to several XSS attacks. Through these vulnerabilities, an attacker could tamper with page rendering, redirect victims to a fake login page, or capture user credentials (such as cookies). With the potential backdoor upload an attacker could gain access to the server itself, to an extent mainly limited by the server setup.\n\n### Reflected Cross-Site Scripting (SXSS) with authentication\nA Neos backend user with permission to modify content can insert JavaScript instructions into content elements. The browser will execute the script in \"Print\" preview mode.\nA Neos backend user who can modify his profile information (\"Title\", \"First Name\", \"Last name\", \"Middle Name\", \"Other Name\") can inject JavaScript instructions in those parameters. Once set up, an administrator who wants to edit this user account will execute the code.\nBoth attack vectors require a valid Neos backend user account.\n\n### Reflected Cross-Site Scripting (RXSS) without authentication\nA non-persistent XSS using parameters passed during plugin execution is possible. If invalid parameters are passed, an error message may be shown (depending on the context Neos runs in and how the parameters are handled) that contains the unescaped parameter value.\n\nNote: Through the HTML content type the inclusion of arbitrary JavaScript is still possible for users with a valid Neos backend account. If you want to prohibit that, disable the nodetype or restrict access.\n\n### Potential backdoor upload\nThrough an issue with the underlying Flow framework (see the related Flow advisory Flow-SA-2015-001) any editor with access to the Media Management module can upload server side script files (when using Neos 2.0.x). If those scripts are executed by the server when accessed through their public URL, anything not blocked through other means is possible (information disclosure, placement of backdoors, data removal, …).",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neos/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.2.0"
      }, {
        "fixed" : "1.2.13"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "neos/neos"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "2.0.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/FriendsOfPHP/security-advisories/blob/master/neos/neos/2015-11-23.yaml"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/neos/neos"
  }, {
    "type" : "WEB",
    "url" : "https://www.neos.io/blog/neos-sa-2015-002.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-05-17T23:04:02Z",
    "nvd_published_at" : null
  }
}