Shopware Platform/Storefront 404 Page cache containing sensitive information

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Shopware Platform and Storefront. It has been classified as problematic. This affects an unknown part of the component 404 Page Handler. Performing a manipulation results in use of cache containing sensitive information. This vulnerability is cataloged as CVE-2024-27917. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Shopware Platform and Storefront (unknown version). It has been classified as problematic. This affects an unknown code block of the component 404 Page Handler. The manipulation with an unknown input leads to a use of cache containing sensitive information vulnerability. CWE is classifying the issue as CWE-524. The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. This is going to have an impact on confidentiality, integrity, and availability.

The weakness was shared 03/06/2024. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-27917 since 02/28/2024. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 7.5
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Use of cache containing sensitive information
CWE: CWE-524
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: github.com
Patch: github.com

Timelineinfo

02/28/2024 🔍
03/06/2024 +7 days 🔍
03/06/2024 +0 days 🔍
09/10/2025 +553 days 🔍

Sourcesinfo

Advisory: 7d9cb03225efca5f97e69b800d8747598dd15ce3
Status: Confirmed

CVE: CVE-2024-27917 (🔍)
GCVE (CVE): GCVE-0-2024-27917
GCVE (VulDB): GCVE-100-255939

Entryinfo

Created: 03/06/2024 19:00
Updated: 09/10/2025 18:01
Changes: 03/06/2024 19:00 (36), 04/05/2024 08:33 (18), 04/05/2024 08:36 (12), 09/10/2025 18:01 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!