Cisco Data Center Network Manager JBoss EAP Unauthorized Access Vulnerability

A vulnerability in the application environment of Cisco Data Center Network Manager (DCNM) could allow an authenticated, remote attacker to gain unauthorized access to the JBoss Enterprise Application Platform (JBoss EAP) on an affected device.

The vulnerability is due to an incorrect configuration of the authentication settings on the JBoss EAP. An attacker could exploit this vulnerability by authenticating with a specific low-privilege account. A successful exploit could allow the attacker to gain unauthorized access to the JBoss EAP, which should be limited to internal system accounts.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

This advisory is available at the following link:

Security Impact Rating: Medium

CVE: CVE-2019-15999


Category for domain and URL context does not match

I need a solution

I have a problem that client need to access to

I have submit this URL to WebPulse and I have got this email.

So I notify client to test but still cannot access to web. I have trace policy for this website but it still appear category as None

*I have already check this URL in proxy and it’s already have category

So I submit to WebPulse as well but I have got this email.

Is that mean when proxy check for category it will check in order like this:



DCS Prevention policy to block WebLogic Exploits?

I need a solution

I know they have been around for a few months already, but I received a request to mitigate against Oracle WebLogic vulnerabilities CVE-2019-2725 and CVE-2019-2729 that were reported being exploited back around April 2019, by using DCS:SA IPS policies.  Admittedly, we’ve only really used DCS:SA for FIM (IDS), but have applied IPS policies for OS/kernel hardening for EOL OS’s.

Does anyone have experience with applying an IPS policy to specifically mitigate WebLogic or point us in the right direction on how best to apply a targetted prevention policy in this situation, while letting WebLogic still function?