Saturday, April 5, 2025
HomeCiscoCisco IOS XE Software Vulnerabilities Let Hackers Gain Root Access in...

Cisco IOS XE Software Vulnerabilities Let Hackers Gain Root Access in Cisco Devices

Published on

SIEM as a Service

Follow Us on Google News

Cisco released a security update for multiple vulnerabilities that affected Cisco IOS XE Software web-based user interface (Web UI) that allows a remote attacker to execute commands with elevated privileges on the vulnerable system.

Cisco IOS XE Software is an internetworking operating system for enterprise networks and is using in several Cisco devices such as Some Cisco routers (such as ASR 1000) and some Catalyst switches (such as 3850).

This Vulnerable software running Cicso deployed in various Enterprise Networks, data centers, and smaller businesses and the potential attacker exploit the vulnerable devices remotely.

According to the Cisco update, These two ( CVE-2019-12650) ( CVE-2019-12651 ) vulnerabilities are not dependent on one another and the attacker no need to exploit one vulnerability to take over another vulnerability.

Both vulnerabilities affected Cisco devices that running vulnerable IOS XE Software release with the HTTP Server feature enabled.

Command Injection Vulnerabilities

A first vulnerability (CVE-2019-12651) with web-based user interface (Web UI) of Cisco IOS XE Software allows low privileged attackers possibly execute the arbitrary command on the vulnerable devices that running with Cisco IOS to elevate privileges.

Another vulnerability (CVE-2019-12650) that affected the web-based user interface (Web UI) due to improperly sanitizes user-supplied input of Cisco IOS XE Software allows remote attackers to execute commands on the underlying Linux shell of vulnerable devices and gain the root access.

According to the Cisco security update, Due to the improperly sanitizes user-supplied input in Cisco IOS, an attacker could exploit this vulnerabilities by supplying a crafted input parameter on a form in the Web UI and then submitting that form.

Customers recommended to disabling the HTTP Server feature eliminates the attack vector for these vulnerabilities until upgrade the system and apply the patch released by Cisco.

Following command will help to check and shows the output will confirm that it has the HTTP Server feature enabled.

Router# show running-config | include ip http server|secure-server
ip http server
ip http secure-server

If you find the presence of either command indicate that the HTTP Server feature is enabled.

If both http server and http-secure server are in use, then both commands are required to disable the HTTP Server feature.

In this case, Cisco adviced to using the following command in global configuration mode. no ip http server or no ip http secure-server.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity and hacking news updates

Also Read: Top 7 Vulnerability Database Sources to Trace New Vulnerabilities

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Ivanti Fully Patched Connect Secure RCE Vulnerability That Actively Exploited in the Wild

Ivanti has issued an urgent security advisory for CVE-2025-22457, a critical vulnerability impacting Ivanti...

Beware! Weaponized Job Recruitment Emails Spreading BeaverTail and Tropidoor Malware

A concerning malware campaign was disclosed by the AhnLab Security Intelligence Center (ASEC), revealing...

EncryptHub Ransomware Uncovered Through ChatGPT Use and OPSEC Failures

EncryptHub, a rapidly evolving cybercriminal entity, has come under intense scrutiny following revelations of...

PoisonSeed Targets CRM and Bulk Email Providers in New Supply Chain Phishing Attack

A sophisticated phishing campaign, dubbed "PoisonSeed," has been identified targeting customer relationship management (CRM)...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Vite Development Server Flaw Allows Attackers Bypass Path Restrictions

A critical security vulnerability, CVE-2025-31125, has been identified in the Vite development server.Due to improper...

Critical Apache Parquet Vulnerability Allows Remote Code Execution

A severe vulnerability has been identified in the Apache Parquet Java library, specifically within...

Halo ITSM Vulnerability Lets Attackers Inject Malicious SQL Code

A critical security flaw has been discovered in Halo ITSM, an IT support management software...