← Back
CVE-2013-10075
critical
CVSS 9.1
Vulnerability in apache (CVE-2013-10075)
Summary
vulnerability in apache (CVE-2013-10075). Confidential information can be exposed externally.
AI summary openai / gpt-4o
A critical vulnerability exists in Apache::Session versions up to 1.94, where sessions thought to be deleted can be recreated. This issue can lead to unintentional revival of data that should have been deleted, posing a risk of personal information leakage. If such a vulnerability is exploited, it could significantly impact users of online services. Utilizing Apache::Session::Store::DBI is a recommended workaround.
Apache::Session up to version 1.94 is vulnerable to session recreation where deleted sessions can be revived. Attackers can exploit this using Apache::Session::Store::File and Apache::Session::Store::DB_File, risking resurrection of data intended for deletion. Affected version is through 1.94, with no fixed version specified. A recommended workaround is to use a store based on Apache::Session::Store::DBI. The CVSS score is 9.1, indicating possibility of network-based attacks with low complexity, requiring no authentication or user interaction.
❓ What is the problem
Apache::Session versions through 1.94 can recreate deleted sessions, leading to potential data leakage.
📍 Affected scope
Apache::Session::Store::File and Apache::Session::Store::DB_File components.
🔥 Severity
Critical severity, CVSS 9.1 (Network-based attack, low complexity, no authentication, high confidentiality and integrity impact).
🔧 How to fix
Use a database store based on Apache::Session::Store::DBI.
🛡️ Workaround
Apply workaround by switching to Apache::Session::Store::DBI.
🔍 Detection
No specific detection method is provided in the sources.
Related past incidents Similar incidents extracted from past CVEs
Similar session management flaw in the npm package, leading to session hijacking.
Apache Tomcat session persistence issue allowing session ID prediction.
Session fixation vulnerability in certain Ruby on Rails versions.
If this happens at your company Expected impact per business scenario
📌 ECサイトにおけるセッション管理
ユーザーのセッションが侵害され、注文履歴や個人情報が第三者に漏洩する可能性がある。
📌 内部業務システムでの利用
社員のアクセス権が不正に引き継がれ、機密情報が漏洩するリスクがある。
📌 クラウドサービスでのセッション管理
プライベートデータにアクセスするためにセッションが誤って復活し、データ漏洩のリスクが高まる。
Recommended action
即座にApache::Session::Store::DBIへの移行を検討し、実装することを推奨します。
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apache' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `apache` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。