VARBINARY display in SQL Server

Seems to be an easily reproducible bug: in SQL Server databases VARBINARY(MAX) fields are displayed as 0x3F3F3F3F3F3F3F3F3F3F3F3F... regardless of the actual value.

Which server version?

SQL Server 2017 Developer edition (the latest image that is currently available in docker: microsoft/mssql-server-windows-developer:latest)

Ok, I did not yet test anything with the 2017 version, but it should not behave such different for blobs than older versions. I wonder if that value is generates by the server or if HeidiSQL does so.

When I view the same database in SQL Server Management Studio, everything is correct.