CVE-2018-20242: Cross-site Scripting in jspwiki-war

Summary

12/02/2019
Yes i
Moderate
6.1

CVE-2018-20242: Cross-site Scripting in jspwiki-war. Affects org.apache.jspwiki:jspwiki-war versions < 2.11.0.M1. Fixed in 2.11.0.M1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The jspwiki-war package is an Apache JSPWiki web application that provides a collaborative platform for creating and editing content. It is built using the Maven ecosystem. The package allows users to create and manage wiki pages, with features such as version control, access control, and plugins. However, versions up to 2.10.5 of jspwiki-war are vulnerable to a cross-site scripting (XSS) attack.

Vulnerability Detail

The vulnerability in jspwiki-war allows an attacker to execute arbitrary JavaScript code in the context of a victim's browser. By crafting a malicious URL, an attacker can inject and execute malicious scripts, potentially leading to session hijacking. This can result in unauthorized access to sensitive information or the manipulation of user sessions. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level.

How To Fix

Minimum fixed version

2.11.0.M1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version is not immediately feasible, a temporary workaround is to sanitize user input before displaying it in the application. Implement input validation and output encoding to prevent the execution of malicious scripts. Here is an example of how to sanitize user input in Java:

import org.apache.commons.lang.StringEscapeUtils;

public class Sanitizer {
  public static String sanitize(String input) {
    return StringEscapeUtils.escapeHtml(input);
  }
}

Conclusion

The jspwiki-war package, up to version 2.10.5, is vulnerable to a cross-site scripting (XSS) attack. This can lead to session hijacking and unauthorized access to sensitive information. To fix this vulnerability, it is recommended to upgrade to version 2.11.0.M1 or later. If immediate upgrading is not possible, implement input validation and output encoding to sanitize user input. For further support, contact DevNack.com.

See every vulnerability recorded for org.apache.jspwiki:jspwiki-war →

Share this vulnerability

FAQ

The vulnerability allows an attacker to execute arbitrary JavaScript code in the victim's browser, potentially leading to session hijacking and unauthorized access to sensitive information.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your pom.xml file and Vulert will analyze it for open-source vulnerabilities in real-time.

Yes, upgrading to version 2.11.0.M1 or later of the jspwiki-war package fixes this vulnerability. Update the package in your project's Maven configuration file (pom.xml) and rebuild your application.

If immediate upgrading is not possible, you can implement input validation and output encoding to sanitize user input and prevent the execution of malicious scripts. See the 'workaround' section for an example in Java.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in fixing this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.jspwiki:jspwiki-war.

How To Fix

Minimum fixed version

2.11.0.M1

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback