Small Business Srp520 Series FirmwareApplication · Cisco
CVE-2012-0365
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 · uneditedDirectory traversal vulnerability in the Local TFTP file-upload application on Cisco SRP 520 series devices with firmware before 1.1.26 and SRP 520W-U and 540 series devices with firmware before 1.2.4 allows remote authenticated users to upload software to arbitrary directories via unspecified vectors, aka Bug ID CSCtw56009.
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 confidenceDirectory traversal vulnerability in the Local TFTP file-upload application on Cisco SRP 520 series (pre-1.1.26) and SRP 520W-U/540 series (pre-1.2.4) routers allows remote authenticated users to upload software to arbitrary directories by manipulating file paths, potentially enabling arbitrary code execution or complete system compromise.
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
Small Business Srp520 Series FirmwareApplication
<= 1.01.24= 1.01.01= 1.01.09= 1.01.11= 1.01.19= 1.01.23
Small Business Srp521wHardware / appliance
all versions
Small Business Srp526wHardware / appliance
all versions
Small Business Srp527wHardware / appliance
all versions
Small Business Srp520 U Series FirmwareApplication
= 1.1.0
Small Business Srp521w UHardware / appliance
all versions
Small Business Srp526w UHardware / appliance
all versions
Small Business Srp527w UHardware / appliance
all versionsCVSS 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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:S/C:C/I:C/A:C
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 Cisco SRP router modelAccess the router administration interface or check the physical device label to determine if it is an SRP520, SRP520W-U, SRP521w, SRP526w, SRP527w, or related U-series variantAffected if The model is any SRP520 series (including SRP521w, SRP526w, SRP527w) or SRP520W-U/540 series before further version checks
-
Check the installed firmware versionLog into the router web interface or CLI and navigate to the firmware version or system status page. Compare the displayed version number against the affected ranges: SRP520 series <= 1.01.24 or specific listed versions; SRP520W-U/540 series < 1.2.4; U-series models (521w U, 526w U, 527w U) all versions are affectedAffected if The firmware version falls within or below 1.01.24 for SRP520 series, is 1.1.0 for SRP520 U series, is any version for SRP521w/526w/527w (all versions), or is below 1.2.4 for SRP520W-U/540 series
-
Determine if TFTP service is enabledAccess the router administration interface and check the TFTP or file transfer service configuration settings. Verify whether the Local TFTP application is turned on or accessibleAffected if The TFTP file-upload feature is enabled and accessible on the device
-
Assess network exposure of the TFTP serviceReview firewall rules, ACLs, or port forwarding settings that control access to the router TFTP service (typically UDP port 69). Determine if the service is reachable from untrusted network segments or the internetAffected if The TFTP service is exposed to untrusted or public network segments without proper access restrictions
A user is affected if they are running any of the vulnerable SRP router models with a firmware version matching the affected ranges and the TFTP service is enabled and accessible to the attacker.
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 · scopedUpgrade Cisco SRP firmware to version 1.1.26 or later for SRP 520 series, or 1.2.4 or later for SRP 520W-U/540 series. If immediate patching is not possible, restrict TFTP service access to trusted administrative users only.
SRP 520 series: firmware 1.1.26 or later; SRP 520W-U/540 series: firmware 1.2.4 or later
- 1. Identify the exact Cisco SRP device model and current firmware version by accessing the device web interface or checking the device label
- 2. For SRP 520 series devices: upgrade firmware to version 1.1.26 or later
- 3. For SRP 520W-U and 540 series devices: upgrade firmware to version 1.2.4 or later
- 4. Download firmware only from the official Cisco support website (tools.cisco.com)
- 5. Access the device administration web interface, navigate to the Administration or System section
- 6. Locate the firmware upgrade option and upload the new firmware file
- 7. Allow the device to complete the upgrade process without power interruption
- 8. After reboot, verify the new firmware version is installed and test that the TFTP functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Small Business Srp520 Series Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0365 — 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-2012-0365 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