Appdynamics ControllerApplication · Cisco
CVE-2024-20346
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in the web-based management interface of Cisco AppDynamics Controller could allow an authenticated, remote attacker to perform a reflected cross-site scripting (XSS) attack against a user of the interface of an affected device. This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit this vulnerability by persuading a user to click a malicious link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA reflected cross-site scripting (XSS) vulnerability exists in the web-based management interface of Cisco AppDynamics Controller due to insufficient validation of user-supplied input. An authenticated attacker can craft malicious links that, when clicked by a user, execute arbitrary JavaScript code in the context of the affected interface, potentially allowing access to sensitive browser-based information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Appdynamics ControllerApplication
< 23.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed AppDynamics Controller versionAccess the Controller's web-based management interface and navigate to the Help or About section, or use the controller's CLI/management tools to query the current software versionAffected if The displayed version number is lower than 23.4.0 (for example, 23.1.0, 22.x, or earlier releases)
-
Confirm web-based management interface is accessibleVerify that the Controller's web UI is enabled and reachable on the configured port (default 8090 or 443)Affected if The web interface is exposed and users can authenticate to it
-
Compare installed version against affected rangeDocument the exact version number and confirm it falls within the vulnerable range of versions prior to 23.4.0Affected if The installed version is any release below 23.4.0 (for example, 23.3.x, 23.2.x, 22.10.x, etc.)
The environment is affected if the Cisco AppDynamics Controller version is below 23.4.0 and the web-based management interface is accessible to users who could click a crafted malicious link.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.4.0
Apply the vendor patch when released; as a temporary measure, implement input validation and output encoding on the affected interface parameters and educate users to avoid clicking untrusted links.
23.4.0 or later
- Backup the AppDynamics Controller configuration and data before upgrading
- Download AppDynamics Controller version 23.4.0 or later from Cisco's official download portal
- Review the 23.4.0 release notes for any specific upgrade prerequisites or migration requirements
- Execute the controller upgrade following Cisco's standard upgrade procedure for AppDynamics Controller
- Verify the controller services start successfully and the UI is accessible after upgrade
- Confirm the upgrade was successful by checking the Controller version in the UI or via CLI
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Appdynamics Controller
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data