Errors testing new connector to CHv 8 – “Connection Error: A failure occurred connecting to Citrix Hypervisor. Error = write EPROTO 140247625111360:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol”

In the XenCenter configuration for the host, uncheck the option to force only TLS 1.2 communication. See the section, “disabling older protocols”, in the below doc.

https://www.citrix.com/content/dam/citrix/en_us/documents/white-paper/security-recommendations-when-deploying-citrix-xenserver.pdf


To correct the cert errors, when unchecking the connector setting, “ignore certificate errors”, follow the below article.

https://support.citrix.com/article/CTX261855

Related:

  • No Related Posts

Cisco Adaptive Security Appliance Software SSL VPN Denial of Service Vulnerability

A vulnerability in the Secure Sockets Layer (SSL) VPN feature of Cisco Adaptive Security Appliance (ASA) Software could allow an authenticated, remote attacker to cause a denial of service (DoS) condition that prevents the creation of new SSL/Transport Layer Security (TLS) connections to an affected device.

The vulnerability is due to incorrect handling of Base64-encoded strings. An attacker could exploit this vulnerability by opening many SSL VPN sessions to an affected device. The attacker would need to have valid user credentials on the affected device to exploit this vulnerability. A successful exploit could allow the attacker to overwrite a special system memory location, which will eventually result in memory allocation errors for new SSL/TLS sessions to the device, preventing successful establishment of these sessions. A reload of the device is required to recover from this condition. Established SSL/TLS connections to the device and SSL/TLS connections through the device are not affected.

Note: Although this vulnerability is in the SSL VPN feature, successful exploitation of this vulnerability would affect all new SSL/TLS sessions to the device, including management sessions.

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-20191002-asa-ssl-vpn-dos

This advisory is part of the October 2019 Cisco ASA, FMC, and FTD Software Security Advisory Bundled Publication, which includes 10 Cisco Security Advisories that describe 18 vulnerabilities. For a complete list of the advisories and links to them, see Cisco Event Response: October 2019 Cisco ASA, FMC, and FTD Software Security Advisory Bundled Publication.

Security Impact Rating: High

CVE: CVE-2019-12677

Related:

  • No Related Posts

What’s the traffic flow in case of an inline IPS and an inline Proxy SG?

I need a solution

Hi;

If I had an IPS device connected inline with the SSL V, and next inline of the SSL V is a Proxy SG.

Does the SSL “https” stream that arrives from the Internet, does it get decrypted by the SSLV to be sent to the IPS, which in case a clean traffic, returns it to the SSLV to be encrypted again and then re-decrypted to be sent to the Proxy SG, which in turn if the traffic is allowed, sends it back to the SSLV to be encrypted again and sent to the internal “LAN”?

Kindly

Wasfi

0

Related:

  • No Related Posts

Cisco Webex Meetings Mobile (iOS) SSL Certificate Validation Vulnerability

A vulnerability in Cisco Webex Meetings Mobile (iOS) could allow an unauthenticated, remote attacker to gain unauthorized read access to sensitive data by using an invalid Secure Sockets Layer (SSL) certificate.

The vulnerability is due to insufficient SSL certificate validation by the affected software. An attacker could exploit this vulnerability by supplying a crafted SSL certificate to an affected device. A successful exploit could allow the attacker to conduct man-in-the-middle attacks to decrypt confidential information on user connections to the affected 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-20190821-webex-ssl-cert

Security Impact Rating: Medium

CVE: CVE-2019-1948

Related:

  • No Related Posts

Cisco Firepower Threat Defense Software File Policy Bypass Vulnerability

A vulnerability in the Secure Sockets Layer (SSL)/Transport Layer Security (TLS) protocol inspection engine of Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to bypass the configured file policies on an affected system.

The vulnerability is due to errors when handling specific SSL/TLS messages. An attacker could exploit this vulnerability by sending crafted HTTP packets that would flow through an affected system. A successful exploit could allow the attacker to bypass the configured file policies and deliver a malicious payload to the protected network.

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-20190807-ftd-bypass

Security Impact Rating: Medium

CVE: CVE-2019-1970

Related:

  • No Related Posts

VM's Power State Does Not Update And Shows As “Unknown” After vCenter Server Reboots

This is an issue with Citrix hypervisor communication library plugin since version Xenapp/XenDesktop version 7.16.

When vCenter server goes alive after reboot i.e “https://<vCenter FQDN>/sdk” becomes accessible, BrokerHostingPlugin still fails to login the vCenter server with exception “The session is not authenticated.”.

CDF Traces from Delivery Controller

,BrokerHostingPlugin,,0,,1,Information,”Attempting connection”,””

,BrokerHostingPlugin,,0,,1,Information,”***** Get Hypervisor Certificate for Connection to ‘https://<vCenter FQDN>/sdk​​​​​​​’ *****”,””

,BrokerHostingPlugin,,0,,1,Information,”Certificate is untrusted: False”,””

,BrokerHostingPlugin,,0,,1,Information,”Time elapsed to get the hypervisor certificate: xxms”,””

,BrokerHostingPlugin,,0,,1,Information,”***** Login Connection – 0 to ‘​​​​​​​https://<vCenter FQDN>/sdk’ as ‘#login_name#‘ *****”,””

,BrokerHostingPlugin,,0,,1,Information,”VMware plugin initialisation times: create service xms, content time xxxms, total xxxms”,””

,BrokerHostingPlugin,,0,,1,Information,”Connected to ‘VMware vCenter Server #vCenter version info#’“,””

,BrokerHostingPlugin,,0,,1,Error,”System.Web.Services.Protocols.SoapException: The session is not authenticated.

,BrokerHostingPlugin,,0,,1,Information,”Connection attempt threw exception System.Web.Services.Protocols.SoapException: The session is not authenticated.

,BrokerHostingPlugin,,0,,1,Information,”Connection is still down”,””

,BrokerHostingPlugin,,0,,1,Information,”Sleeping for 00:00:30 before trying to reconnect again”,””

Related:

  • No Related Posts

Cisco ASA and FTD Software Cryptographic TLS and SSL Driver Denial of Service Vulnerability

A vulnerability in the cryptographic driver for Cisco Adaptive Security Appliance Software (ASA) and Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause the device to reboot unexpectedly.

The vulnerability is due to incomplete input validation of a Secure Sockets Layer (SSL) or Transport Layer Security (TLS) ingress packet header. An attacker could exploit this vulnerability by sending a crafted TLS/SSL packet to an interface on the targeted device. An exploit could allow the attacker to cause the device to reload, which will result in a denial of service (DoS) condition.

Note: Only traffic directed to the affected system can be used to exploit this vulnerability. This vulnerability affects systems configured in routed and transparent firewall mode and in single or multiple context mode. This vulnerability can be triggered by IPv4 and IPv6 traffic. A valid SSL or TLS session is required to exploit this vulnerability.

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-20190710-asa-ftd-dos

Security Impact Rating: High

CVE: CVE-2019-1873

Related:

  • No Related Posts

Anti tampering featurer is not being installed properly for unified agent

I need a solution

Hi;

When I install the MSI using the command:

bcuaXX-setup.msi /qn CM_URL=https://proxysgip:8084 SUP=123456 FORCEREBOOT=no, the installation succeedes but the anti-tampering feature does not work. So when the user tries to uninstall the unified agent, she/he does not get asked for the anti-tampering password.

Kindly

Wasfi

0

1559623199

Related:

  • No Related Posts

“Time out reached while waiting for …. SepMasterService” error, causing virtual machine freezes?

I need a solution

i have a Windows Server 2012 virtual machine that will freeze up and require a full system restart every few days. Before the freeze up occurred,  errors in Event Viewer show “A time out (30000 milliseconds) was reached while waiting for a transaction response from the SepMasterService service.”

what is causing this error, and could it be resulting in a system freeze?

Could it also interfere with the operation of other programs on my machine? Because at other times, a web server program will cease working properly and will need to be restarted. The web server’s TCP port is seen as open, but any attempt to access the web page it services results in a blank screen. 

This series of errors appears to be the only troubleshooting clue in Event Viewer.

i saw a closed topic similar to this one posted last year  here: 

https://www.symantec.com/connect/forums/timeout-60000-milliseconds-waiting-transaction-response-sepmasterservice-service-0

although a tech support person from Symantec comments in the thread, the solution is not mentioned. Anyone else seen this issue and have a fix for it?

0

Related:

  • No Related Posts

Invalid certificate

I need a solution

Hello guys, 

The client request to the google.com then client and server weren’t complete communication with google certificate. The problem is if client request to any website then using bluecoat certificate and the browser couldn’t verify that certificate. In ssl client configuriation include custom keyring and support for TLSv1.2, TLSv1.1, TLSv1, SSLv3* ssl protocols.

Thank you guys!

0

1559110145

Related:

  • No Related Posts