GeoNode up to 4.2.2 Rich Text Editor cross site scripting

Summaryinfo

A vulnerability has been found in GeoNode up to 4.2.2 and classified as problematic. This vulnerability affects unknown code of the component Rich Text Editor. Performing a manipulation results in cross site scripting. This vulnerability is identified as CVE-2024-27091. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in GeoNode up to 4.2.2. It has been classified as problematic. This affects an unknown part of the component Rich Text Editor. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-79. 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. This is going to have an impact on integrity. The summary by CVE is:

GeoNode is a geospatial content management system, a platform for the management and publication of geospatial data. An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. This vulnerability is fixed in 4.2.3.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-27091 since 02/19/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

Upgrading to version 4.2.3 eliminates this vulnerability. Applying the patch e53bdeff331f4b577918927d60477d4b50cca02f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• GeoNode

Version

• 4.2.0
• 4.2.1
• 4.2.2

License

• open-source

Website

• Product: https://github.com/GeoNode/geonode/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion