VeriStand 2021 R3 Bug Fixes

Overview

The following items are notable issues fixed between the release of VeriStand 2021 R2 and VeriStand 2021 R3, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of VeriStand.

Bug Number

Legacy ID

Description

Details

1888724

Rapid gateway address update prevents deployment

Opening a project and immediately changing the gateway address to an invalid IP address may cause VeriStand to retain the invalid IP gateway address and ignore all further gateway address updates. This system state may prevent successful deployment.

Workaround:

Close and reopen the project. Wait 10 seconds after loading the project before modifying the gateway IP address.

Reported Version:

VeriStand 2020 R6

Resolved Version:

VeriStand 2021 R3

Added:

Apr 15, 2022

1934224

VeriStand does not apply T=0 value to FMUs

FMUs with an initial condition value of T=0 do not have that value applied by VeriStand. Initial values are ignored. The first model execution iteration corresponded to y=f(t), where t=dt. This effectively skips t=0.

Workaround:

There is no known workaround for this issue.

Reported Version:

VeriStand 2019

Resolved Version:

VeriStand 2021 R3

Added:

Oct 4, 2022

1946550

VeriStand hangs when mapping many connections to the same node

VeriStand may not respond when interacting with a file that maps multiple connections to a single node. This can occur under the following conditions:
  • Importing a mapping file
  • Loading a project file

Workaround:

  1. On the mapping diagram, ensure that the source channel terminals of the pending import mappings are not displayed.
  2. Edit the mapping file so that an additional, distinct source channel exists in the list of mappings for each mapping pair. 
  3. Use System Explorer to import the mapping file.

Reported Version:

VeriStand 2020 R4

Resolved Version:

VeriStand 2021 R3

Added:

Oct 4, 2022

2068953

VeriStand Target Log Viewer only displays the first line of messages

The VeriStand Target Log Viewer (introduced in 2021) only displays the first line of a multi-lined message.

Workaround:

Log each line individually. This method is slower than logging one message with multiple lines.

For more information, refer to the VeriStand Custom Device Handbook section on LabVIEW Debugging Techniques.

Reported Version:

VeriStand 2021

Resolved Version:

VeriStand 2021 R3

Added:

Oct 4, 2022

Fix Security Issue for CVE-2024-6805: Missing Authorization Checks in VeriStand Gateway

The VeriStand Gateway does not perform authorization checks when the users attempt to access it's services. This may result in information disclosure or remote code execution.

Workaround:

To ensure the security of the VeriStand Gateway on your system against unauthorized remote access, adhere to the guidelines in this document.

Reported Version:

VeriStand 2021 R3

Resolved Version:

VeriStand 2021 R3 Patch 2

Added:

N/A

Fix Security Issues for CVE-2024-6675 and CVE-2024-6793: Deserialization of Untrusted Data in VeriStand

Deserialization of untrusted data may result in remote code execution while opening a project, using data logging and waveform streaming services of VeriStand Gateway

Workaround:

There is currently no known workaround for this issue.

Reported Version:

VeriStand 2021 R3

Resolved Version:

VeriStand 2021 R3 Patch 2

Added:

N/A

Fix Security Issue for CVE-2024-6791: Susceptibility to "directory traversal attack" when loading vsmodels

A directory path traversal vulnerability exists when loading a vsmodel file in VeriStand that may result in remote code execution.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

VeriStand 2021 R3

Resolved Version:

VeriStand 2021 R3 Patch 2

Added:

N/A

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).