11.4. What’s Fixed in 7.1.0

11.4.1. Recording Service reported an exception when recording or replaying type registered as a union

Publishing a union type instead of a structure type caused Recording Service to report an exception. This was a regression from the previous release, where union was a valid type for Recording Service. This problem has been resolved.

[RTI Issue ID RECORD-1339]

11.4.2. Recording Service Crashed if -maxObjectsPerThread set too small

Recording Service crashed if the command-line option -maxObjectsPerThread had a value less than 1024. This issue, which also affected Routing Service, has been resolved. Now instead of crashing, the service will log the following warning and the default value will be used.

Max objects per thread can't be lower than 1024. Setting MaxObjectsPerThread to 1024.

[RTI Issue ID ROUTING-1024]

11.4.3. Fixes Related to Vulnerabilities

11.4.3.1. Recording Service crashed when loading a malicious XML configuration file

Due to a vulnerability in SQLite, the XML configuration tag sql_initialization_string was used by Recording Service without proper input validation. This issue could cause Recording Service to crash during service startup.

This vulnerability was fixed by upgrading SQLite to version 3.39.4. See What’s New in 7.1.0 for additional information.

11.4.3.1.1. User Impact without Security

An improper validation of array index in Recording Service could have resulted in the following:

• Recording Service crashed.

• Exploitable by loading a malicious XML configuration file.

• CVSS v3.1 Score: 3.3 LOW

• CVSS v3.1 Vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

11.4.3.1.2. User Impact with Security

Same as User Impact without Security.

[RTI Issue ID RECORD-1374]

11.4.4. Fixes Related to Usability

11.4.4.1. The Instance History Replay feature did not publish all relevant samples

Before starting normal replay, the Instance History Replay feature did not publish the full state of the world for keyed topics. An issue storing the instance history index prevented Replay Service from finding all the samples to include in the state-of-the-world dataset. This issue has been resolved.

[RTI Issue ID RECORD-1370]

11.4.4.2. Unexpected ERROR prefix in Converter Service standard logs

An unexpected “ERROR” prefix appeared in the Converter Service logs. For example:

ERROR Stream [Square]: total samples written = 536
ERROR Stream [Circle]: total samples written = 473
ERROR Stream [Triangle]: total samples written = 408

This issue has been resolved. The logs now display as follows:

Stream [Square]: total samples written = 536
Stream [Circle]: total samples written = 473
Stream [Triangle]: total samples written = 408

[RTI Issue ID RECORD-1363]