Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-1247: Exposure of Data Element to Wrong Session

0
High
VulnerabilityCVE-2025-1247cvecve-2025-1247
Published: Thu Feb 13 2025 (02/13/2025, 13:26:26 UTC)
Source: CVE Database V5

Description

A flaw was found in Quarkus REST that allows request parameters to leak between concurrent requests if endpoints use field injection without a CDI scope. This vulnerability allows attackers to manipulate request data, impersonate users, or access sensitive information.

AI-Powered Analysis

AILast updated: 11/11/2025, 16:06:18 UTC

Technical Analysis

CVE-2025-1247 is a vulnerability identified in the Quarkus REST framework, a popular Java-based framework used for building microservices and RESTful applications. The flaw arises when endpoints use field injection without specifying a Context and Dependency Injection (CDI) scope, which leads to request parameters leaking between concurrent requests. Essentially, the framework fails to isolate request data properly, causing data from one user's session to be accessible in another user's session. This can result in attackers manipulating request data, impersonating other users, or gaining unauthorized access to sensitive information. The vulnerability is exploitable remotely over the network with low attack complexity and does not require user interaction, making it a serious threat. The CVSS v3.1 score of 8.3 reflects high confidentiality and integrity impacts, with a low availability impact. Although no exploits have been reported in the wild yet, the vulnerability's nature suggests that it could be leveraged for session hijacking, data leakage, and privilege escalation in affected applications. The root cause is the improper use of field injection without CDI scope, which is a common development oversight. This vulnerability underscores the importance of correctly managing dependency injection scopes in Java microservices frameworks to ensure request data isolation and session integrity.

Potential Impact

For European organizations, the impact of CVE-2025-1247 can be significant, especially for those relying on Quarkus REST for critical business applications, including financial services, healthcare, and government services. The leakage of request parameters between concurrent sessions can lead to unauthorized data disclosure, user impersonation, and potential regulatory non-compliance under GDPR due to exposure of personal data. Integrity of data can be compromised, allowing attackers to manipulate transactions or application behavior. Although availability impact is low, the reputational damage and potential financial losses from data breaches or fraud could be substantial. Organizations with multi-tenant applications or those handling sensitive user data are particularly at risk. The vulnerability also raises concerns about trust in microservices architectures if dependency injection is not properly managed. Given the high adoption of Java frameworks in Europe’s software industry, the threat could affect a broad range of sectors and applications.

Mitigation Recommendations

To mitigate CVE-2025-1247, European organizations should: 1) Immediately review and update their Quarkus REST applications to ensure that all field injections specify an appropriate CDI scope, such as @RequestScoped, to isolate request data properly. 2) Avoid using field injection without scope or switch to constructor or method injection where appropriate. 3) Apply any available patches or updates from Quarkus or Red Hat as soon as they are released. 4) Conduct thorough code audits focusing on dependency injection practices and concurrency handling in REST endpoints. 5) Implement runtime monitoring and anomaly detection to identify unusual request patterns that may indicate exploitation attempts. 6) Educate developers on secure coding practices related to CDI scopes and injection in microservices. 7) Use security testing tools to simulate concurrent requests and verify that data leakage does not occur. 8) Limit exposure by enforcing strict access controls and authentication mechanisms on REST endpoints. These steps go beyond generic advice by focusing on the root cause—improper CDI scope usage—and proactive detection.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
redhat
Date Reserved
2025-02-12T09:43:11.716Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68af0c87ad5a09ad00627bd4

Added to database: 8/27/2025, 1:47:51 PM

Last enriched: 11/11/2025, 4:06:18 PM

Last updated: 12/4/2025, 1:56:22 PM

Views: 98

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats