CVE-2023-7104
A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.
- T
Tim Bastin detected CVE-2023-7104 with a risk of 3.35
System updated the risk assessment to 2.54
System recalculated raw risk assessment
- T
Tim Bastin fixed CVE-2023-7104
- T
Tim Bastin detected CVE-2023-7104 with a risk of 2.54
System updated the risk assessment to 1.27
System recalculated raw risk assessment
System updated the risk assessment to 2.54
System recalculated raw risk assessment
System updated the risk assessment to 1.27
System recalculated raw risk assessment
- T
Tim Bastin detected CVE-2023-7104 with a risk of 1.27
System updated the risk assessment from 1.27 to 0.85
System recalculated raw risk assessment
System updated the risk assessment from 1.27 to 0.85
System recalculated raw risk assessment
System updated the risk assessment from 0.85 to 2.54
System recalculated raw risk assessment
System updated the risk assessment from 0.85 to 2.54
System recalculated raw risk assessment
System
System fixed CVE-2023-7104
System
System detected CVE-2023-7104 with a risk of 2.54
System
System
System fixed CVE-2023-7104
System
System detected CVE-2023-7104 with a risk of 2.54
- T
Tim Bastin detected CVE-2023-7104 with a risk of 2.54
- T
Tim Bastin detected CVE-2023-7104 with a risk of 2.54
- T
Tim Bastin detected CVE-2023-7104 with a risk of 2.54
- T
Tim Bastin detected CVE-2023-7104 with a risk of 2.54
- T
Tim Bastin
System updated the risk assessment from 1.27 to 2.54
System recalculated raw risk assessment
- T
Tim Bastin fixed CVE-2023-7104
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.54 to 2.75
Confidentiality Requirement updated: medium -> low, Integrity Requirement updated: medium -> high, Availability Requirement updated: medium -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
- S
Sebastian Kawelke updated the risk assessment from 2.75 to 3.05
Confidentiality Requirement updated: low -> high
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System fixed CVE-2023-7104
System detected CVE-2023-7104 with a risk of 3.05
Add a comment
Affected component
debian/sqlite3