LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43271: Riverbed AppResponse 11.8.0, 11.8.5, 11.8.5a, 11.9.0, 11.9.0a, 11.10.0, 11.11.0, 11.11.0a, 11.11.1, 11.11.1...

Riverbed AppResponse 11.8.0, 11.8.5, 11.8.5a, 11.9.0, 11.9.0a, 11.10.0, 11.11.0, 11.11.0a, 11.11.1, 11.11.1a, 11.11.5, and 11.11.5a (when configured to use local, RADIUS, or TACACS authentication) logs usernames and passwords if either is entered incorrectly. If a user enters an incorrect username and/or password when logging into the WebUI, these attempted credentials are included in an error message that is logged in the WebUI log file. A log entry does not appear if the username and password provided correctly match a valid set of credentials. This also does not happen if AppResponse is configured to use SAML authentication. The WebUI log file is included in subsequent diagnostic system dumps that are generated. (Only users with Full Control access to the System Configuration permission can generate system dumps. By default, only System Administrators have Full Control access to the System Configuration permission.)

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue can leak mistyped login credentials into Riverbed AppResponse WebUI logs. The business risk is credential exposure through logs or diagnostic dumps, not direct remote takeover. Exposure is limited to listed AppResponse versions using local, RADIUS, or TACACS authentication.

Executive priority

Prioritize if AppResponse manages sensitive network monitoring environments or if diagnostic dumps have been shared. This is mainly a credential hygiene and access-control issue, but exposed credentials can enable broader compromise.

Technical view

Riverbed AppResponse versions 11.8.0, 11.8.5 variants, 11.9.0 variants, 11.10.0, and 11.11.x through 11.11.5a log incorrect WebUI username/password attempts. Correct credentials are not logged. SAML authentication is not affected. Diagnostic system dumps include the WebUI log file.

Likely exposure

Organizations are exposed if they run the listed AppResponse versions and use local, RADIUS, or TACACS authentication. Risk increases where WebUI logs or diagnostic dumps are broadly accessible, retained long-term, or shared externally for support.

Exploitation context

The provided sources do not show active exploitation, public exploit use, or KEV listing. Abuse would depend on access to WebUI logs or diagnostic dumps containing failed login attempts.

Researcher notes

The vulnerability condition is specific: failed WebUI login attempts with local, RADIUS, or TACACS auth. Correct logins do not create entries. Evidence does not include CVSS, CWE, patch version details, or exploitation reports in the supplied bundle.

Mitigation direction

  • Review Riverbed advisory S35806 for fixed releases or vendor-approved remediation.
  • Consider SAML authentication where operationally appropriate; the source says SAML is not affected.
  • Restrict System Configuration Full Control access to trusted administrators only.
  • Treat WebUI logs and diagnostic dumps as sensitive credential-bearing data.
  • Rotate passwords found in affected logs or diagnostic dumps.

Validation and detection

  • Inventory AppResponse appliances and compare versions against the affected list.
  • Confirm whether authentication uses local, RADIUS, TACACS, or SAML.
  • Review who can generate and access diagnostic system dumps.
  • Search retained WebUI logs and support dumps for exposed attempted credentials.
  • Verify remediation against Riverbed guidance after changes are applied.
Prepared
Confidence
high
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-43271 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.