blackduck complaining about critical security risk

[sara66]

we are using latest version of rapidjson in our project and running blakduck scan results in showing critical security risk pointing to rapidjson folder but complaining about cereal11 1.3 component which is not used in the project!

Any idea what should be done about it? is there any version that does not have this issue?

here is the full description of security risk:

"An issue was discovered in USC iLab cereal through 1.3.0. It employs caching of std::shared_ptr values, using the raw pointer address as a unique identifier. This becomes problematic if an std::shared_ptr variable goes out of scope and is freed, and a new std::shared_ptr is allocated at the same address. Serialization fidelity thereby becomes dependent upon memory layout. In short, serialized std::shared_ptr variables cannot always be expected to serialize back into their original values. This can have any number of consequences, depending on the context within which this manifests."