CVE-2013-10075
Session Revival Vulnerability in Apache::Session for Perl
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: CPANSec
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| chorny | apache | to 1.94 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-672 | The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Apache::Session versions through 1.94 for Perl, where deleted sessions can be re-created. Specifically, the session stores Apache::Session::Store::File and Apache::Session::Store::DB_File may create sessions that were previously deleted, effectively reviving sessions that should no longer exist.
As a result, data that was intended to be deleted from these sessions might still be accessible or restored unintentionally.
How can this vulnerability impact me? :
The impact of this vulnerability is that sessions which were deleted can be revived, potentially exposing sensitive or outdated session data that should have been removed.
This can lead to unauthorized access to session information, confusion in session management, and possible security risks if sensitive data is restored unintentionally.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows deleted sessions to be re-created, potentially reviving session data that was intended to be deleted.
Such behavior can lead to retention of personal or sensitive data beyond its intended lifecycle, which may conflict with data protection requirements in regulations like GDPR and HIPAA that mandate proper deletion and protection of user data.
Therefore, the vulnerability could negatively impact compliance by undermining data deletion policies and increasing the risk of unauthorized access to supposedly deleted session information.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, it is recommended to avoid using the vulnerable session stores Apache::Session::Store::File and Apache::Session::Store::DB_File, which can recreate deleted sessions.
A suggested workaround is to switch to using a database store based on Apache::Session::Store::DBI, which does not exhibit this issue.