Cisco does not fix 74 bugs in RV routers that have reached their EOL

Cisco said yesterday that it would not release firmware updates to fix 74 vulnerabilities reported to exist in RV routers that have reached the end of their life cycle (EOL).

Affected devices include Cisco Small Business RV110W, RV130, RV130W and RV215W systems, which can be used as both routers or firewalls and as VPNs. All four systems reached their EOL in 2017 and 2018.

In three security advisories published yesterday, Cisco said that since December, it has received bug reports for vulnerabilities ranging from simple issues. denial of service to security vulnerabilities that could be exploited by them hacker to access root accounts and to invade routers.

In total, Cisco said it received 74 bug reports, but that it would not release software patches, mitigations or solutions as Appliances had long ago reached their EOL.

Instead, the company advised customers to move to newer devices, such as the RV132W, RV160 or RV160W models, which provide them with exactly the same possibilities and which are still supported actively from company.

Some of the customers may not like the company decision, but the good news is that none of these errors can be utilized easily.

Cisco said all vulnerabilities require an attacker to have them credentials of the device, which reduces the risk of attacks on networks in the coming weeks or months, giving administrators the opportunity to design and prepare a relocation plan to a newer equipment, or at least to develop their own countermeasures.

The CVE of errors that Cisco refused to fix on the routers are listed below:

• CVE-2021-1146
• CVE-2021-1147
• CVE-2021-1148
• CVE-2021-1149
• CVE-2021-1150
• CVE-2021-1151
• CVE-2021-1152
• CVE-2021-1153
• CVE-2021-1154
• CVE-2021-1155
• CVE-2021-1156
• CVE-2021-1157
• CVE-2021-1158
• CVE-2021-1159
• CVE-2021-1160
• CVE-2021-1161
• CVE-2021-1162
• CVE-2021-1163
• CVE-2021-1164
• CVE-2021-1165
• CVE-2021-1166
• CVE-2021-1167
• CVE-2021-1168
• CVE-2021-1169
• CVE-2021-1170
• CVE-2021-1171
• CVE-2021-1172
• CVE-2021-1173
• CVE-2021-1174
• CVE-2021-1175
• CVE-2021-1176
• CVE-2021-1177
• CVE-2021-1178
• CVE-2021-1179
• CVE-2021-1180
• CVE-2021-1181
• CVE-2021-1182
• CVE-2021-1183
• CVE-2021-1184
• CVE-2021-1185
• CVE-2021-1186
• CVE-2021-1187
• CVE-2021-1188
• CVE-2021-1189
• CVE-2021-1190
• CVE-2021-1191
• CVE-2021-1192
• CVE-2021-1193
• CVE-2021-1194
• CVE-2021-1195
• CVE-2021-1196
• CVE-2021-1197
• CVE-2021-1198
• CVE-2021-1199
• CVE-2021-1200
• CVE-2021-1201
• CVE-2021-1202
• CVE-2021-1203
• CVE-2021-1204
• CVE-2021-1205
• CVE-2021-1206
• CVE-2021-1207
• CVE-2021-1208
• CVE-2021-1209
• CVE-2021-1210
• CVE-2021-1211
• CVE-2021-1212
• CVE-2021-1213
• CVE-2021-1214
• CVE-2021-1215
• CVE-2021-1216
• CVE-2021-1217
• CVE-2021-1307
• CVE-2021-1360

Source of information: zdnet.com