FIX handling of CAN device interface names #1715
5 new issues (0 max.) of at least minor severity.
Here is an overview of what got changed by this pull request:
Issues
======
- Added 5
Complexity increasing per file
==============================
- modules/HardwareDrivers/PowerSupplies/UUGreenPower_UR1000X0/can_driver_acdc/CanDevice.cpp 3
- modules/HardwareDrivers/PowerSupplies/InfyPower_BEG1K075G/can_driver_acdc/CanDevice.cpp 3
- lib/everest/io/src/can/socket_can_handler.cpp 1
See the complete overview on Codacy
Annotations
Check failure on line 110 in lib/everest/io/src/can/socket_can_handler.cpp
codacy-production / Codacy Static Code Analysis
lib/everest/io/src/can/socket_can_handler.cpp#L110
Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120).
codacy-production / Codacy Static Code Analysis
modules/HardwareDrivers/PowerSupplies/InfyPower_BEG1K075G/can_driver_acdc/CanDevice.cpp#L32
Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126).
codacy-production / Codacy Static Code Analysis
modules/HardwareDrivers/PowerSupplies/InfyPower_BEG1K075G/can_driver_acdc/CanDevice.cpp#L45
Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120).
codacy-production / Codacy Static Code Analysis
modules/HardwareDrivers/PowerSupplies/UUGreenPower_UR1000X0/can_driver_acdc/CanDevice.cpp#L32
Does not handle strings that are not \0-terminated; if given one it may perform an over-read (it could cause a crash if unprotected) (CWE-126).
codacy-production / Codacy Static Code Analysis
modules/HardwareDrivers/PowerSupplies/UUGreenPower_UR1000X0/can_driver_acdc/CanDevice.cpp#L45
Easily used incorrectly; doesn't always \0-terminate or check for invalid pointers [MS-banned] (CWE-120).