Preview Tool

Cisco Bug: CSCur53172 - DOC: ACE30: SFTP transfer and strict host key checking

Last Modified

Nov 27, 2020

Products (1)

  • Cisco Application and Content Networking System (ACNS) Software

Known Affected Releases

3.0(0)A5(2.2) 3.0(0)A5(3.1a)

Description (partial)



This issue is under review by the Cisco Product Security Incident Response
team (PSIRT).

The defect describes a product security vulnerability.  Its contents must
be protected from unauthorized disclosure, both internal and external to
Cisco.  Do not forward this information to mailing lists or newsgroups.

Documentation writers: it is prohibited to publish this Release-note 
Enclosure (RNE) until the content has been approved by PSIRT.  PSIRT may 
publish a Security Advisory regarding this defect, and the current text of 
this RNE will be replaced with appropriate information.  In the event that 
a Security Advisory is not published, PSIRT will replace this text with an 
appropriate explanation.

More information on PSIRT is available at <http//>.  
Cisco's public policy on security vulnerability handling can be reviewed at 
For further information, send a message to

User: guest-Date:11-27-2020

For SFTP transfers ACE does "Strict Host Key Checking".

Host key for SFTP server changes and no longer match the host key in "known_hosts" file on ACE.

Related Community Discussions

<key>CSCur53172</key> - DOC ACE30: SFTP transfer and strict host key checking
Working on a ACE30-MOD-K9, I came across the following error when trying to SSH to another host from here:   RSA host key for X.X.X.X has changed and you have requested strict checking. Host key verification failed   Problem Description: CU hits <key>CSCur53172</key>   But, the solution is pretty easy...   # clear ssh hosts   This happens when the ACE30 has a pre-existing SSH key stored for the remote device and the remote device's key changes. The command simply clears the buffer of local SSH keys stored for ...
Latest activity: Oct 11, 2018
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.