<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article PSM for SSH: Qualys Scan Utility reports Vulnerability. in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/psm-for-ssh-qualys-scan-utility-reports-vulnerability/ta-p/1427421</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;Customer security team runs Qualys scan on the PSM for SSH (PSMP) servers; and detects a vulnerability related to SSH.&lt;/P&gt;
&lt;P&gt;Example:&lt;/P&gt;
&lt;P&gt;- "SSH User Login Bruteforced"&lt;BR /&gt;-&amp;nbsp; Or reports on an CVE: for an unrelated product IE: https://nvd.nist.gov/vuln/detail/CVE-2020-29583&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;Qualys is typically&amp;nbsp;hitting a 'false' positive.&lt;/P&gt;
&lt;P&gt;The PSM for SSH&amp;nbsp;has a unique SSH connection workflow, for initiating connection through the PSM for SSH server. Qualys&amp;nbsp;is unable to distinguish this workflow within their scanning tool.&lt;/P&gt;
&lt;P&gt;Environment:&lt;BR /&gt;PSM for SSH -&amp;nbsp; PSMP&lt;BR /&gt;Installation method = &amp;nbsp;InstallCyberArkSSHD=Yes&lt;BR /&gt;&lt;BR /&gt;The symptom is that the Qualys' Security Scan&amp;nbsp;is able to initiate an SSH session with the PSMP Server.&lt;BR /&gt;- That is what is being caught by Qualys as the "vulnerability"&lt;BR /&gt;What the Qualys' scanner doesn't do, is proceed through the rest of the PSM for SSH prompts to confirm that the PSMP's authentication process doesn't allow the user to logon without the providing the correct Vault User credentials.&lt;/P&gt;
&lt;P&gt;Example Session Initiation with the PSM Server:&lt;/P&gt;
&lt;P&gt;[caadmin@testsystem&amp;nbsp;~]$ ssh someuser@psmpserver&lt;BR /&gt;someuser@psmpserver's password:&lt;BR /&gt;Target user is required (to use domain account, specify &amp;lt;target_user&amp;gt;#&amp;lt;domain_address&amp;gt;).&lt;BR /&gt;Target user: 'targetuser'&lt;BR /&gt;Target machine address is required (to use port, specify &amp;lt;target_address&amp;gt;#&amp;lt;target_port&amp;gt;).&lt;BR /&gt;Target machine address: 'targetaddress'&lt;BR /&gt;PSPSD072E Perform session error occurred. Reason: PSPSD033E Error receiving PSM For SSH server response (Extra information: [289E [b2a9b3c8-51ed-11eb-823e-2eface977278] Failed to impersonate as user [someuser]. Error: [ITATS004E Authentication failure for User someuser.&lt;BR /&gt;]], [1]). (Codes: -1, 1)&lt;BR /&gt;Connection to psmpserver closed.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Note: In a typical SSH workflow, the end user is not prompted for a "target user" or "target address." after entering their password.&lt;BR /&gt;&lt;BR /&gt;Typical SSH workflow example:&lt;/P&gt;
&lt;P&gt;[caadmin@testserver ~]$ ssh someuser@server&lt;BR /&gt;someuser@server's password:&lt;BR /&gt;Permission denied, please try again.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The Qualys' utility, is hitting a false positive, in thinking it was granted successful&amp;nbsp;logon, because of the PSMP session initiation prompts/process&amp;nbsp;(when not using a completed PSMP connection string), does not immediately&amp;nbsp;provide that&amp;nbsp;the password provided was not valid, ie&amp;nbsp; "Permission denied, please try again.".&lt;BR /&gt;&lt;BR /&gt;Idira recommends testing the reported vulnerability against the PSMP, given the details provided within the Qualys' Report for username and password, to verify the false positive.&lt;/P&gt;</description>
    <pubDate>Thu, 05 Nov 2026 20:12:04 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:12:04Z</dc:date>
    <item>
      <title>PSM for SSH: Qualys Scan Utility reports Vulnerability.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/psm-for-ssh-qualys-scan-utility-reports-vulnerability/ta-p/1427421</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
&lt;P&gt;Customer security team runs Qualys scan on the PSM for SSH (PSMP) servers; and detects a vulnerability related to SSH.&lt;/P&gt;
&lt;P&gt;Example:&lt;/P&gt;
&lt;P&gt;- "SSH User Login Bruteforced"&lt;BR /&gt;-&amp;nbsp; Or reports on an CVE: for an unrelated product IE: https://nvd.nist.gov/vuln/detail/CVE-2020-29583&lt;/P&gt;
&lt;H3&gt;Answer&lt;/H3&gt;
&lt;P&gt;Qualys is typically&amp;nbsp;hitting a 'false' positive.&lt;/P&gt;
&lt;P&gt;The PSM for SSH&amp;nbsp;has a unique SSH connection workflow, for initiating connection through the PSM for SSH server. Qualys&amp;nbsp;is unable to distinguish this workflow within their scanning tool.&lt;/P&gt;
&lt;P&gt;Environment:&lt;BR /&gt;PSM for SSH -&amp;nbsp; PSMP&lt;BR /&gt;Installation method = &amp;nbsp;InstallCyberArkSSHD=Yes&lt;BR /&gt;&lt;BR /&gt;The symptom is that the Qualys' Security Scan&amp;nbsp;is able to initiate an SSH session with the PSMP Server.&lt;BR /&gt;- That is what is being caught by Qualys as the "vulnerability"&lt;BR /&gt;What the Qualys' scanner doesn't do, is proceed through the rest of the PSM for SSH prompts to confirm that the PSMP's authentication process doesn't allow the user to logon without the providing the correct Vault User credentials.&lt;/P&gt;
&lt;P&gt;Example Session Initiation with the PSM Server:&lt;/P&gt;
&lt;P&gt;[caadmin@testsystem&amp;nbsp;~]$ ssh someuser@psmpserver&lt;BR /&gt;someuser@psmpserver's password:&lt;BR /&gt;Target user is required (to use domain account, specify &amp;lt;target_user&amp;gt;#&amp;lt;domain_address&amp;gt;).&lt;BR /&gt;Target user: 'targetuser'&lt;BR /&gt;Target machine address is required (to use port, specify &amp;lt;target_address&amp;gt;#&amp;lt;target_port&amp;gt;).&lt;BR /&gt;Target machine address: 'targetaddress'&lt;BR /&gt;PSPSD072E Perform session error occurred. Reason: PSPSD033E Error receiving PSM For SSH server response (Extra information: [289E [b2a9b3c8-51ed-11eb-823e-2eface977278] Failed to impersonate as user [someuser]. Error: [ITATS004E Authentication failure for User someuser.&lt;BR /&gt;]], [1]). (Codes: -1, 1)&lt;BR /&gt;Connection to psmpserver closed.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Note: In a typical SSH workflow, the end user is not prompted for a "target user" or "target address." after entering their password.&lt;BR /&gt;&lt;BR /&gt;Typical SSH workflow example:&lt;/P&gt;
&lt;P&gt;[caadmin@testserver ~]$ ssh someuser@server&lt;BR /&gt;someuser@server's password:&lt;BR /&gt;Permission denied, please try again.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The Qualys' utility, is hitting a false positive, in thinking it was granted successful&amp;nbsp;logon, because of the PSMP session initiation prompts/process&amp;nbsp;(when not using a completed PSMP connection string), does not immediately&amp;nbsp;provide that&amp;nbsp;the password provided was not valid, ie&amp;nbsp; "Permission denied, please try again.".&lt;BR /&gt;&lt;BR /&gt;Idira recommends testing the reported vulnerability against the PSMP, given the details provided within the Qualys' Report for username and password, to verify the false positive.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2026 20:12:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/psm-for-ssh-qualys-scan-utility-reports-vulnerability/ta-p/1427421</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:12:04Z</dc:date>
    </item>
  </channel>
</rss>

