Affected versions of this crate did not properly check for recursion while deserializing aliases.
This allows an attacker to make a YAML file with an alias referring to itself causing an abort.
The flaw was corrected by checking the recursion depth.
This project might be open to known security vulnerabilities, which can be prevented by tightening the version range of affected dependencies. Find detailed information at the bottom.
lenna_cli(12 total, 9 outdated, 2 possibly insecure)
| Crate | Required | Latest | Status |
|---|---|---|---|
| libloading | ^0.7 | 0.8.6 | out of date |
| structopt | ^0.3 | 0.3.26 | up to date |
| image | ^0.24 | 0.25.6 | out of date |
| pyo3 ⚠️ | ^0.16 | 0.24.2 | out of date |
| ndarray | ^0.15 | 0.16.1 | out of date |
| nshare | ^0.9 | 0.10.0 | out of date |
| numpy | ^0.16 | 0.24.0 | out of date |
| pythonize | ^0.16 | 0.24.0 | out of date |
| serde | ^1.0 | 1.0.219 | up to date |
| serde_json | ^1.0 | 1.0.140 | up to date |
| serde_yaml ⚠️ | ^0.8 | 0.9.34+deprecated | out of date |
| zip | ^0.6 | 2.6.1 | out of date |
serde_yaml: Uncontrolled recursion leads to abort in deserializationAffected versions of this crate did not properly check for recursion while deserializing aliases.
This allows an attacker to make a YAML file with an alias referring to itself causing an abort.
The flaw was corrected by checking the recursion depth.
pyo3: Risk of buffer overflow in `PyString::from_object`PyString::from_object took &str arguments and forwarded them directly to the Python C API without checking for terminating nul bytes. This could lead the Python interpreter to read beyond the end of the &str data and potentially leak contents of the out-of-bounds read (by raising a Python exception containing a copy of the data including the overflow).
In PyO3 0.24.1 this function will now allocate a CString to guarantee a terminating nul bytes. PyO3 0.25 will likely offer an alternative API which takes &CStr arguments.