CVE-2013-10075: Apache::Session versions through 1.94 for Perl re-creates deleted sessions
Apache::Session versions through 1.94 for Perl re-creates deleted sessions.
The session stores Apache::Session::Store::File and Apache::Session::Store::DB_File will create a session that does not exist. This can lead to sessions being revived, potentially with data that was to be deleted.
Security readout for executives and security teams
CVE-2013-10075 affects Apache::Session for Perl. Deleted sessions can be recreated when File or DB_File session stores are used, potentially restoring data that should have been removed. For applications relying on session deletion for logout, account changes, or cleanup, this can create confidentiality and integrity risk. Exposure is likely limited to Perl applications using Apache::Session through 1.94 with File or DB_File stores. Applications that treat session deletion as a security boundary, such as logout or revocation, are most relevant. The provided affected metadata is inconsistent, so inventory validation is important. Prioritize assessment for internet-facing or sensitive Perl applications using Apache::Session. The business risk is unauthorized continuation or restoration of sessions thought to be removed. No active exploitation is cited, but the CVSS rating and security impact justify prompt inventory and remediation planning. Mitigation focus: Identify applications using Apache::Session, especially File or DB_File stores.; Check CPAN/vendor guidance for a fixed version or maintainer-recommended workaround.; Prioritize systems where session deletion enforces logout, revocation, or access changes..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-672: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
4Timeline events
2ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-672 · source CWE mapping
Operation on a Resource after Expiration or Release
Operation on a Resource after Expiration or Release represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.