INCIDENT MAP

Browse / Unsafe Model Loading and Supply Chain / CVE-2022-23577

Null-dereference in Tensorflow

CVE-2022-23577 ยท 2022-02-10 high

Class
Unsafe Model Loading and Supply Chain (filed by a model that read the advisory)
Technique
Denial of service
Affected
tensorflow-cpu, tensorflow (PyPI)
CVSS
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.8% chance of exploitation in 30 days

How it works, in short

A crafted SavedModel with a missing nested signature key makes the loader dereference a null pointer and crash when the model is opened. (Our summary, written by a model. The source text is below.)

Details

Impact

The implementation of GetInitOp is vulnerable to a crash caused by dereferencing a null pointer:

const auto& init_op_sig_it =
    meta_graph_def.signature_def().find(kSavedModelInitOpSignatureKey);
if (init_op_sig_it != sig_def_map.end()) {
  *init_op_name = init_op_sig_it->second.outputs()
                      .find(kSavedModelInitOpSignatureKey)
                      ->second.name();
  return Status::OK();
}

Here, we have a nested map and we assume that if the first .find succeeds then so would be the search in the internal map. However, the maps are built based on the SavedModel protobuf format and a malicious user can alter that on disk before loading to cause the second .find to return nullptr.
### Patches
We have patched the issue in GitHub commit 4f38b1ac8e42727e18a2f0bde06d3bee8e77b250.

The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

References

Source: GitHub Advisory Database, used under CC BY 4.0.