CVE-2023-2749
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 · uneditedDownload Center fails to properly validate the file path submitted by a user, An attacker can exploit this vulnerability to gain unauthorized access to sensitive files or directories without appropriate permission restrictions. Download Center on ADM 4.0 and above will be affected. Affected products and versions include: Download Center 1.1.5.r1280 and below.
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 · moderate confidenceThis is a path traversal vulnerability in Download Center where user-supplied file paths are not properly validated, allowing attackers to use directory traversal sequences (such as '../') to access sensitive files and directories outside the intended download directory. This is a classic input validation failure enabling unauthorized file system access.
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>= 1.1.5, < 1.1.5.r1298CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm Asustor Download Center is installedCheck system applications or package list for 'Download Center' or use the NAS admin interface to verify the application is presentAffected if Download Center application is installed on the Asustor NAS
-
Identify the installed version of Download CenterAccess NAS admin panel, navigate to App Central or the application management section, locate Download Center and record the version number displayedAffected if Version is 1.1.5 or higher but below r1298 (such as 1.1.5.r1280, 1.1.5.r1285, etc.)
-
Verify remote access is enabled for Download CenterCheck Download Center settings or NAS network configuration for remote access, HTTPS, or external access settings that allow the application to be reached over the networkAffected if Remote/network access to Download Center is enabled and the application is exposed to users or attackers
-
Check if download functionality is accessible to untrusted usersReview user permissions and access controls for Download Center to determine if guest users, limited users, or unauthenticated users can input file paths for downloadsAffected if Untrusted or low-privilege users can supply file paths to the download feature
You are affected if Download Center is installed with version 1.1.5 through 1.1.5.r1297 and the download feature with user-supplied file paths is accessible to users beyond trusted administrators.
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 · scoped1.1.5.r1298
Implement strict input validation on file path parameters using allowlist validation, normalize paths to prevent traversal sequences, and ensure proper permission checks are enforced before serving any file. Upgrade to a patched version above 1.1.5.r1280 if available.
Download Center version 1.1.5.r1298 or later
- 1. Identify the current version of Download Center installed on the ADM device
- 2. Access the ADM management interface and navigate to the App Central or Apps section
- 3. Locate Download Center in the list of installed applications
- 4. Check if an update is available - the fixed version is 1.1.5.r1298 or later
- 5. If an update is available, initiate the update process to upgrade Download Center to version 1.1.5.r1298 or newer
- 6. After the update completes, verify the new version is installed correctly
- 7. Test that the Download Center functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2749 — 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-2023-2749 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