Hoene

**Name of the Vulnerable Software and Affected Versions** Symonics libmysofa version 0.7 **Description** The issue is related to an out-of-bounds read in the `directblockRead` function located in `hdf/fractalhead.c`. **Recommendations** For version 0.7, at the moment, there is no information about a newer version that contains a fix for this issue.

**Name of the Vulnerable Software and Affected Versions** Symonics libmysofa version 0.7 **Description** The issue is related to a NULL pointer dereference in the `getHrtf` function located in `hrtf/reader.c`. **Recommendations** For Symonics libmysofa version 0.7, consider applying a patch or fix that addresses the NULL pointer dereference in the `getHrtf` function. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Symonics libmysofa version 0.7 **Description** The issue is related to an invalid write in the `readOHDRHeaderMessageDataLayout` function located in `hdf/dataobject.c`. **Recommendations** For Symonics libmysofa version 0.7, consider applying a patch or fix that addresses the invalid write issue in the `readOHDRHeaderMessageDataLayout` function.

**Name of the Vulnerable Software and Affected Versions** Symonics libmysofa version 0.7 **Description** The issue is related to an invalid read in the `readOHDRHeaderMessageDataLayout` function in `hdf/dataobject.c`. **Recommendations** For Symonics libmysofa version 0.7, consider applying a patch or fix to address the invalid read issue in the `readOHDRHeaderMessageDataLayout` function.

**Name of the Vulnerable Software and Affected Versions** Symonics libmysofa version 0.7 **Description** The issue is related to an invalid read in the `getDimension` function located in `hrtf/reader.c`. This problem can lead to unintended behavior. **Recommendations** For Symonics libmysofa version 0.7, consider restricting access to the `getDimension` function in `hrtf/reader.c` until a patch is available. At the moment, there is no information about a newer version that contains a fix for this issue.