Posted on October 16, 2017
We have discovered a critical issue with certain versions of the Cb Response Binary Detonation integrations released in the last month. A patch that was rolled out to the Binary Detonation integrations in September erroneously submitted corrupt files to the binary detonation providers, potentially resulting in invalid responses from the analysis platform. No sensitive information was leaked as part of this bug. Specifically, the first five bytes of the file were missing on every submission of a file to a binary detonation appliance.
As soon as we identified the issue on Friday, October 13, we quickly re-issued each integration to fix the issue. The affected versions are listed at the end of this note.
We encourage all on-premise users of the Cb Response Binary Detonation Integrations listed below to upgrade to the latest version as soon as possible. We are reaching out to affected Cb Response Cloud customers and scheduling the upgrades to their connectors as necessary.
To determine the versions of your integrations, run the following command on your Cb Response server (or wherever you are running the integration code):
rpm -q -a | grep python-cb- | grep connector
|Integration Name||Affected Version||Fixed Version|
|python-cb-virustotal-connector||1.0-1, 1.0-2, 1.0-3||1.0-4|
If you have affected connectors, run:
yum clean all
to update the OpenSource repository, then:
yum upgrade <integration name>
for each affected integration.
The issue has been fixed in the common Cb Integration code, version 0.9.2.