Cisco Jabber for Windows Protocol Handler Command Injection Vulnerability

A vulnerability in the application protocol handling features of Cisco Jabber for Windows could allow an unauthenticated, remote attacker to execute arbitrary commands.

The vulnerability is due to improper handling of input to the application protocol handlers. An attacker could exploit this vulnerability by convincing a user to click a link within a message sent by email or other messaging platform. A successful exploit could allow the attacker to execute arbitrary commands on a targeted system with the privileges of the user account that is running the Cisco Jabber client software.

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:
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-jabber-vY8M4KGB

Security Impact Rating: High

CVE: CVE-2020-3430

Related:

Modification of pop-up / Alerting messaging

I need a solution

Has anyone had any success in modifying the alerting message being presented to end users when the policy calls for this as part of the response rule?

There are two aspects with this request…

  1. Support for bilingual messages (in my case I need French and English) but I can see this being needed with other languages such as Spanish and English
  2. Messaging on the pop-up must comply with our internal Branding and communication policies which the default does not.

Without this functionality, we cannot proceed in the next step of the strategy of communicating to our constituents that they are about to exfiltrate information that has been deemed not to exit the organization.   Executives have mandated that this must come first before we start actually blocking.

My thoughts are this should be a simple XML file in which the content can be modified to present our specific messages.  Am I wrong?

Thanks….

0

Related:

7023318: Error 0xAD0B on GroupWise Messenger agent and failed Messenger client login for any user

This document (7023318) is provided subject to the disclaimer at the end of this document.

Environment

GroupWise 18

GroupWise Messenger 18

Open Enterprise Server 2018 (OES 2018) Linux

Situation

When Messenger 18 users attempt to login , thed fail and the Messenger agent logs shows the error :

“Login failed [0xAD0B]: LAM – Invalid credentials supplied to LDAP”.
Also and nds trace was done and it shows the errors at attempted login time of :
“Failed to resolve full context on connection 0xf4f8700, err=no such entry (-601)”
“Failed to authenticate full context on connection 0xf4f8700, err=no such entry (-601)”
“Sending operation result 49:””:”NDS error: failed authentication (-669)” to connection 0xf4″

Resolution

It was discovered that the GroupWise MTA object , under the Ldap tab, in the GroupWise Web Admin Console, had LDAP enabled and port 389 selected. However the MTA linux box had Micro Focus Open Enterprise Server (OES2018) installed and it uses port 389 for Ldap services. So there was a port conflict. Once we changed the port under the MTA object to an unused port like 390 and restarted the GroupWise “gwadminservice” the problem went away.

Cause

Ldap port conflict.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

GroupWise Messenger Archiving with Retain!

qmangus

As those who use GroupWise Messenger know, this solution is a great secure instant messaging solution for any organization. GroupWise Messenger allows for real-time chat on desktop or mobile devices. With GroupWise Messenger you can give your users the functionality and features of a public IM tool, but without the risks of those types of tools. And with …

+read more

The post GroupWise Messenger Archiving with Retain! appeared first on Cool Solutions. qmangus

Related:

7023304: Error :The Vibe mail filter experienced a problem.

This document (7023304) is provided subject to the disclaimer at the end of this document.

Environment

GWAVA (Secure Messaging Gateway) 6.5

Situation

After installing GWAVA for Vibe, and a landing page, or a link etc.. is modified in Vibe the following error occurs:

Error
The Vibe mail filter experienced a problem. Please try again or contact the help desk or your system administrator.
Within the appserver log it shows the following error: 2018-08-15 09:47:44,754 ERROR [ajp-nio-8009-exec-26] [org.kablink.teaming.remoting.rest.provider.VibeRuntimeMapper] – An error occurred while processing a REST request (REST request: (testuser@158.69.133.114) GET /files/12c0b4786098ad4f016127ae222331f3)org.kablink.teaming.repository.RepositoryServiceException: Cannot read file “file.jpg” for entry folderEntry_2463119: It does not exist
Within the catalina.out log it shows the following error: 2018-08-10 16:50:53,727 WARN [ajp-nio-8009-exec-481] [org.kablink.teaming.remoting.rest.provider.VibeRuntimeMapper] – An error occurred while processing a REST request (REST request: (testuser@32.66.87.121) GET /files/12c0b4785fce0cd50160122571596424) org.kablink.teaming.domain.NoFileByTheIdException: No such file by the id ’12c0b4785fce0cd50160122571596424′

Resolution

Download this new teamGwava.jar file and replace it with the existing one found in: /opt/novell/teaming/apache-tomcat/lib/custom-ext.



The new jar file will also be in the latest update of GWAVA 6.5.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7022740: An active Vibe user stops showing up in the users list. Re-index returns an error

This document (7022740) is provided subject to the disclaimer at the end of this document.

Environment

Micro Focus Vibe 4.0.4

Micro Focus Vibe 4.0.3

Micro Focus Vibe 4.0.2

Novell Vibe 4.0.1

Novell Vibe 4.0

Situation

An active Vibe user stops showing up in the users list. When a re-index is performed on the “Users and Groups” area, an error similar to the one shown below is seen in the appserver.log file.

2018-01-01 11:11:11,987 ERROR [http-bio-80-exec-8] [org.kablink.teaming.module.profile.impl.DefaultProfileCoreProcessor] – Error indexing entry: (12345) John Doe

org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: org.kablink.teaming.domain.UserPrincipal.memberOf, no session or session was closed

Resolution

A fix for this issue is available for Vibe 4.0.2 -Patch 2. Please contact Micro Focus Customer Care with reference to this TID for further assistance.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

….messagelabs.com Connection timed out

I need a solution

Hello,

like some others, I have a problem with messaging via messagelabs.com.
 

connect to cluster1.eu.messagelabs.com[193.109.254.67]:25: Connection timed out
connect to cluster2a.eu.messagelabs.com[85.158.139.103]:25: Connection timed out
connect to cluster3.eu.messagelabs.com[85.158.137.67]:25: Connection timed out
connect to cluster4a.eu.messagelabs.com[85.158.139.103]:25: Connection timed out
connect to cluster8.eu.messagelabs.com[85.158.140.211]:25: Connection timed out

Our mailserver with IP 138.201.200.181 is not on the blacklist.
What can i do to resolve this problem?

regards Ralf

0

Related: