Skip to content

Commit 6035ac4

Browse files
committed
initial
1 parent a614e99 commit 6035ac4

File tree

2 files changed

+19
-1
lines changed

2 files changed

+19
-1
lines changed

articles/defender-for-iot/organizations/release-notes.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,13 @@ This version includes the following updates and enhancements:
114114

115115
- [Sensor time drift detection](whats-new.md#sensor-time-drift-detection)
116116
- Bug fixes for stability improvements
117+
- The following CVEs are resolved in this version:
118+
- CVE-2024-29055
119+
- CVE-2024-29054
120+
- CVE-2024-29053
121+
- CVE-2024-21324
122+
- CVE-2024-21323
123+
- CVE-2024-21322
117124

118125
### Version 24.1.2
119126

articles/defender-for-iot/organizations/whats-new.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,13 +21,24 @@ Features released earlier than nine months ago are described in the [What's new
2121
|Service area |Updates |
2222
|---------|---------|
2323
| **OT networks** | [Sensor time drift detection](#sensor-time-drift-detection) |
24+
| | [Security updates](#security-update) |
2425

2526
### Sensor time drift detection
2627

27-
This version introduces a new troubleshooting test in the connectivity tool feature, specifically designed to identify time drift issues.
28+
This version introduces a new troubleshooting test in the connectivity tool feature, specifically designed to identify time drift issues.
2829

2930
One common challenge when connecting sensors to Defender for IoT in the Azure portal arises from discrepancies in the sensor’s UTC time, which can lead to connectivity problems. To address this issue, we recommend that you configure a Network Time Protocol (NTP) server [in the sensor settings](configure-sensor-settings-portal.md#ntp).
3031

32+
### Security update
33+
34+
This version resolves the following CVEs:
35+
- CVE-2024-29055<br>
36+
- CVE-2024-29054<br>
37+
- CVE-2024-29053<br>
38+
- CVE-2024-21324<br>
39+
- CVE-2024-21323<br>
40+
- CVE-2024-21322<br>
41+
3142
## February 2024
3243

3344
|Service area |Updates |

0 commit comments

Comments
 (0)