01-06-2019 11:22 PM - edited 03-08-2019 04:57 PM
Running image cat4500-ipbasek9-mz.150-2.SG11.bin we have faced vulnerabilities
CVE-2015-6375 |
CVE-2015-0204 |
CVE-2017-3881 |
cisco-sa-20170419 |
cisco-sa-20170629 |
CVE-2017-6770 |
CVE-2017-12240 |
CVE-2018-0174 |
CVE-2018-0175 |
CVE-2018-0172 |
CVE-2018-0173 |
CVE-2018-0167 |
CVE-2018-15369 |
CVE-2018-15373 |
CVE-2018-0197 |
CVE-2018-0475 |
i had checked all CVE ids there is no work around. also installed image latest only. how can i fix this issue any one help this bug fix?
Solved! Go to Solution.
01-08-2019 12:18 AM
Thanks for sharing the config. Having checked it against the vulnerabilities listed see below:
CVE-2015-6375 - CNS not configured
CVE-2015-0204 - openSSL - Vulnerable - no workaround
CVE-2017-3881 - cluster - vulnerable - mitigate by disabling clustering or implementing VTY ACLs
cisco-sa-20170419 - generic advisory
cisco-sa-20170629 - snmpv2c - vulnerable - the attacked would need to know your couity string AND by permitted by ACL 17
CVE-2017-6770 - OSPF - not configured, not vulnerable
CVE-2017-12240 - DHCP relay - vulnerable - no workaround
CVE-2018-0174 - DHCP relay - vulnerable - no workaround
CVE-2018-0175 - LLDP - not configured, not vulnerable
CVE-2018-0172 - DHCP relay - vulnerable - no workaround
CVE-2018-0173 - DHCP relay - vulnerable - no workaround
CVE-2018-0167 - LLDP - not configured, not vulnerable
CVE-2018-15369 - TACACS client - vulnerable
CVE-2018-15373 - CDP - not configured, not vulnerable
CVE-2018-0197 - VTP - vulnerable
CVE-2018-0475 - cluster - vulnerable
Anything marked vulnerable can only be revolved by software upgrade. Since this is not an option, you wil have to either upgrade the supervisor card or replace the entire chassis with one which runs a patched version of IOS/ IOS-XE/ NX-OS.
cheers,
Seb.
01-06-2019 11:26 PM
@sankardevarajan1986 wrote:
how can i fix this issue any one help this bug fix?
Easy: Upgrade the IOS
01-06-2019 11:29 PM
running image cat4500-ipbasek9-mz.150-2.SG11.bin
can you suggest which version needs to upgrade?
01-06-2019 11:56 PM
What supervisor engine are you using in the chassis. Some have been EOL'd and therefore there is no chance of new software being made available.
I did a quick check of some of those vulnerabilities, are you sure you are usig the specific features listed? If they are not in use, that is as good as having a workaround implemented! :)
cheers,
Seb.
01-07-2019 12:04 AM
Catalyst 4500E 7 slot chassis for 48Gbps/slot,
could you explain what is specific features listed?
01-07-2019 12:06 AM
What is the output of:
sh module
01-07-2019 02:30 AM
this is vulnerability issue. we need to upgrade or downgrade the image or need to restrict enabled commands.
01-07-2019 02:42 AM
I'd like to know what supervisor you are running to determine if it has been EOL'd which will affect your chances of getting another software release ever being published for your switch.
If a newer software release is not an option then the only mitigation is to upgrade the platform, either the supervisor (or entire chassis), to one which has a software release which mitigates all of these vulnerabilities.
As I said in my first post, have you confirmed you have actually implemented the features which are susceptible to these CVEs?? There is no need to panic about them if you are not exposed.
Cheers,
Seb
01-07-2019 03:09 AM
sh module
Chassis Type : WS-C4507R+E
Power consumed by backplane : 40 Watts
Mod Ports Card Type Model Serial No.
---+-----+--------------------------------------+------------------+-----------
1 6 1000BaseX (GBIC) WS-X4306-GB JAE1002TE45
2 6 1000BaseX (GBIC) WS-X4306-GB JAE1002TE3S
3 6 Sup V-10GE 10GE (X2), 1000BaseX (SFP) WS-X4516-10GE JAE14200F16
4 6 Sup V-10GE 10GE (X2), 1000BaseX (SFP) WS-X4516-10GE JAE1016071D
5 48 10/100/1000BaseT (RJ45) WS-X4548-GB-RJ45 JAE0952SRVY
6 48 10/100/1000BaseT (RJ45) WS-X4548-GB-RJ45 JAE1001T4QU
M MAC addresses Hw Fw Sw Status
--+--------------------------------+---+------------+----------------+---------
1 000f.2494.ec04 to 000f.2494.ec09 4.1 Ok
2 000f.2494.ebe6 to 000f.2494.ebeb 4.1 Ok
3 d8b1.90b1.d280 to d8b1.90b1.d285 5.4 12.2(31r)SGA 15.0(2)SG11 Ok
4 d8b1.90b1.d286 to d8b1.90b1.d28b 3.6 12.2(31r)SGA 15.0(2)SG11 Ok
5 0016.9d13.6710 to 0016.9d13.673f 2.2 Ok
6 0016.9d13.bb40 to 0016.9d13.bb6f 2.2 Ok
Mod Redundancy role Operating mode Redundancy status
----+-------------------+-------------------+----------------------------------
3 Standby Supervisor SSO Standby hot
4 Active Supervisor SSO Active
01-07-2019 03:36 AM
Thanks. See:
...there will be no further software updates for this supervisor. It does give a replacement part number:WS-X45-SUP7-E which has software released as recently as September 2018.
It may be cheaper to evaluate your configuration and determine if you are actually vulnerable to the CVEs you listed above.
cheers,
Seb.
01-07-2019 03:53 AM
Thank you so much for timing reply. I have checked mentioned those vulnerabilities, no work around from Cisco.
could you please help to fix these vulnerabilities.
01-07-2019 04:04 AM
Can you share the config of the switch so we can pick our way through it?
01-07-2019 04:14 AM
no cluster run command - if i configured any imapact shall be happen
01-07-2019 04:40 AM
I've never used clustering, so can't comment. I'd imagine if you remove that command any changes made to the cluster will ot be propagated to that switch.
You should be able to get the running config without removing it from the cluster.
01-08-2019 12:18 AM
Thanks for sharing the config. Having checked it against the vulnerabilities listed see below:
CVE-2015-6375 - CNS not configured
CVE-2015-0204 - openSSL - Vulnerable - no workaround
CVE-2017-3881 - cluster - vulnerable - mitigate by disabling clustering or implementing VTY ACLs
cisco-sa-20170419 - generic advisory
cisco-sa-20170629 - snmpv2c - vulnerable - the attacked would need to know your couity string AND by permitted by ACL 17
CVE-2017-6770 - OSPF - not configured, not vulnerable
CVE-2017-12240 - DHCP relay - vulnerable - no workaround
CVE-2018-0174 - DHCP relay - vulnerable - no workaround
CVE-2018-0175 - LLDP - not configured, not vulnerable
CVE-2018-0172 - DHCP relay - vulnerable - no workaround
CVE-2018-0173 - DHCP relay - vulnerable - no workaround
CVE-2018-0167 - LLDP - not configured, not vulnerable
CVE-2018-15369 - TACACS client - vulnerable
CVE-2018-15373 - CDP - not configured, not vulnerable
CVE-2018-0197 - VTP - vulnerable
CVE-2018-0475 - cluster - vulnerable
Anything marked vulnerable can only be revolved by software upgrade. Since this is not an option, you wil have to either upgrade the supervisor card or replace the entire chassis with one which runs a patched version of IOS/ IOS-XE/ NX-OS.
cheers,
Seb.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide