CVE-2024-29720
Information Disclosure in Sciter v4.4.7.0 Adopt Video Component
Publication date: 2025-12-26
Last updated on: 2025-12-26
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| terra_informatica_software_inc | sciter | 4.4.7.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Terra Informatica Software, Inc Sciter v.4.4.7.0 allows a local attacker to obtain sensitive information through the adopt component of the Sciter video rendering function.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized disclosure of sensitive information by a local attacker exploiting the adopt component in the video rendering function.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by analyzing the usage of the `AssetPtr::<T>::get` function in the Rust `rust-sciter` library, specifically looking for unsafe pointer casts where the type `T` has smaller alignment or size than `iasset`. One way to detect this is by running the vulnerable code under the Rust interpreter `miri`, which can catch undefined behavior related to pointer dereferencing. For example, running a test similar to the provided code snippet under `miri` will trigger an error if the vulnerability is present. The example command to run the test under miri is: `cargo miri run` after setting up a test case that uses `AssetPtr::adopt` with a smaller type like `u8`. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding or disabling the use of the `AssetPtr::<T>::get` function with types `T` that have smaller alignment or size than `iasset`. Reviewing and patching the code to ensure safe pointer casts and proper alignment checks before dereferencing pointers is essential. Additionally, running code analysis tools like `miri` to detect unsafe behavior can help prevent exploitation. If a patch or update from the vendor is available, applying it promptly is recommended. [1]