CVE-2014-3526: Apache Wicket Sensitive Data Exposure

Summary

13/05/2022
Yes i
High
7.5

CVE-2014-3526: Apache Wicket Sensitive Data Exposure. Affects org.apache.wicket:wicket-core across 3 version ranges.

< 1.5.12 >= 6.0, < 6.17.0 >= 7.0.0-M1, < 7.0.0-M3

Fixed in 1.5.12, 6.17.0 or 7.0.0-M3, depending on the release line you run. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Apache Wicket is an open-source Java web application framework that simplifies the development of dynamic web applications. It provides a component-based programming model and supports various features such as form handling, validation, and AJAX. The vulnerability in Apache Wicket versions before 1.5.12, 6.x before 6.17.0, and 7.x before 7.0.0-M3 allows remote attackers to obtain sensitive information through identifiers used for storing page markup in temporary user sessions.

Vulnerability Detail

The vulnerability in Apache Wicket arises from the way it handles identifiers for storing page markup in temporary user sessions. Remote attackers can exploit this vulnerability to gain access to sensitive information. The impact of this vulnerability can be significant, as it may expose sensitive data to unauthorized individuals. The vulnerability has a CVSS score of 7.5, indicating a high severity level.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.5.12 1.5.12
  • >= 6.0, < 6.17.0 6.17.0
  • >= 7.0.0-M1, < 7.0.0-M3 7.0.0-M3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is advised to apply the recommended fix by upgrading to the secure versions mentioned above.

Conclusion

The vulnerability in Apache Wicket allows remote attackers to obtain sensitive information, potentially leading to unauthorized access to confidential data. It is crucial to apply the recommended fix by upgrading to the secure versions mentioned above. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.wicket:wicket-core →

Share this vulnerability

FAQ

Apache Wicket is an open-source Java web application framework that simplifies the development of dynamic web applications.

The vulnerability allows remote attackers to obtain sensitive information, potentially exposing confidential data to unauthorized individuals.

The CVSS score of this vulnerability is 7.5, indicating a high severity level.

To fix this vulnerability, it is recommended to upgrade to the secure versions of Apache Wicket mentioned in the 'how_to_fix' section.

No, there is no known workaround for this vulnerability. Applying the recommended fix by upgrading to the secure versions is the best course of action.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.wicket:wicket-core.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.5.12 1.5.12
  • >= 6.0, < 6.17.0 6.17.0
  • >= 7.0.0-M1, < 7.0.0-M3 7.0.0-M3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. 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