TELTONIKA NETWORKING DEVICES
Saugumo Centras
Bet kuris prie Interneto prijungtas įrenginys gali tapti kibernetinių atakų taikiniu. Čia pateikiame visą informaciją apie bet kokią egzistuojančią ar potencialią saugumo spragą, kuri yra susijusi su mūsų įrenginiais.
cURL multiple vulnerabilities patched
22-12-13
Multiple vulnerabilities were remediated as cURL was patched to version 7.86.0 in RutOS 7.3 firmware.
Several cURL vulnerabilities were discovered in RUTOS, ranging from LOW to MEDIUM severity
CVE-2022-42915 CVE-2022-32221 CVE-2022-35252
POST following PUT confusion; HTTP proxy double-free; control code in cookie denial of service
Linux Kernel Wi-Fi vulnerabilities remediated with 7.3
22-10-05
Vulnerabilities are patched with our RutOS 7.3 firmware, as such it is advised to update your firmware to the latest one available.
5 WiFi CVE's discovered in total:
CVE-2022-41674 CVE-2022-42719 CVE-2022-42720 CVE-2022-42721 CVE-2022-42722
Vulnerabilities stem from holes triggered by "Beacon Frames".
Any Linux device vulnerable to these exploits would be susceptible to attacks when scanning for a network if a rogue AP was present.
Title
Description
Title and description
- 4 puslapis
NEWS & ARTICLES
Secure Software Development Lifecycle
Ensuring the security of our products and services is a top priority at Teltonika. They are designed, developed, and rigorously tested with security and privacy in mind throughout the software development lifecycle of each release.
In addition to performing vulnerability management, reviewing vulnerability reports, routine monitoring of new vulnerabilities, and handling vulnerability remediation, Teltonika’s core Secure Software Development Lifecycle (SSDL) consists of the following phases:
Training
As a pre-requirement of this lifecycle, Teltonika’s security team drafts training materials and developer test on a yearly basis.
Requirements
Baseline security and privacy requirements for the upcoming release are drafted and communicated internally.
Design
Software design reviews are conducted with the goals of understanding the upcoming release, drafting.
Implementation
Static code scanning tools are maintained and code is reviewed.
Verification
Comprehensive fuzzing, penetration, and final security tests are performed.
Release
Documents are finalised, archived, and taken into account for the following cycle.
