Appdynamics ControllerApplication · Cisco
CVE-2024-20345
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 file upload functionality of Cisco AppDynamics Controller could allow an authenticated, remote attacker to conduct directory traversal attacks on an affected device. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted request to an affected device. A successful exploit could allow the attacker to access sensitive data on an affected device.
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 confidenceThe vulnerability exists in the file upload functionality of Cisco AppDynamics Controller, where insufficient validation of user-supplied input allows authenticated remote attackers to conduct directory traversal attacks. An attacker can send crafted requests to access sensitive data outside the intended directory boundaries on the affected device.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed AppDynamics Controller versionAccess the Controller UI Administration page or run: curl -k https://<controller-host>/controller/rest/serverversion. Compare the returned version number to the affected range (< 23.4.0).Affected if Installed version is lower than 23.4.0
-
Confirm file upload functionality is accessibleCheck if the Controller allows file uploads through the UI or API endpoints such as /controller/FileUpload. Verify the endpoint responds and accepts requests.Affected if File upload endpoints are exposed and accessible without additional restrictions beyond authentication
-
Verify authentication configurationReview Controller authentication settings to confirm user authentication is enforced. Check if default or weak credentials are in use, and review the list of authenticated users with file upload permissions.Affected if Untrusted or compromised accounts have file upload privileges, or authentication is minimally configured
-
Inspect server logs for traversal attemptsSearch Controller logs (located in <appserver_home>/logs) for patterns such as '../', '..\', '%2e%2e', or directory traversal payloads in file upload requests. Review access logs for suspicious upload patterns.Affected if Logs contain directory traversal patterns in file upload requests from any user account
-
Check file system permissions on Controller directoriesReview file system permissions on the Controller's upload directories and adjacent sensitive directories. Verify that uploaded files cannot escape the intended upload folder.Affected if File permissions allow uploaded files to exist outside the designated upload directory
The environment is affected if the installed AppDynamics Controller version is below 23.4.0 and the file upload functionality is accessible to authenticated users.
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-provided patch from Cisco when available. Until then, restrict file upload permissions to only trusted, authenticated users and monitor for suspicious file upload patterns indicating traversal attempts.
23.4.0 or later
- Obtain AppDynamics Controller version 23.4.0 or later from the official Cisco/AppDynamics download portal
- Review the AppDynamics Controller upgrade documentation for your deployment type
- Execute the upgrade following Cisco's documented upgrade procedure
- Verify the Controller is running version 23.4.0 or later post-upgrade
- Confirm the file upload functionality is working correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Appdynamics Controller
Scoped from the published advisory
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20345 — 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-20345 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