CVE-2025-0697
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, which was classified as problematic, was found in Telstra Smart Modem Gen 2 up to 20250115. This affects an unknown part of the component HTTP Header Handler. The manipulation of the argument Content-Disposition leads to injection. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA Content-Disposition HTTP header injection vulnerability exists in Telstra Smart Modem Gen 2 firmware up to January 2025. The issue affects the HTTP Header Handler component where improper input validation of the Content-Disposition header argument allows injection of malicious content. This is a remote attack vector with medium severity (CVSS 5.3).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm device modelAccess the modem administration interface or check the device label to verify the exact model is Telstra Smart Modem Gen 2Affected if Device is not a Telstra Smart Modem Gen 2
-
Check firmware versionLog into the modem web interface (typically at 192.168.0.1 or 192.168.1.1) and navigate to Administration or System settings to view the firmware version. Alternatively, check via telnet or SSH if enabled: 'show version' or 'cat /proc/version'Affected if Firmware version is from January 2025 or earlier (any version up to and including the January 2025 release)
-
Verify HTTP management interface accessibilityConfirm whether the modem's web-based administration interface is accessible from the WAN/internet side by attempting to access the device IP from an external network, or check port 80/443 is open to external IPs via 'nmap -p 80,443 <wan-ip>'Affected if HTTP management interface is exposed to untrusted networks (WAN side)
-
Identify input validation behavior on Content-DispositionSend a crafted HTTP request with an abnormal Content-Disposition header to the modem's web interface (e.g., using curl: curl -H 'Content-Disposition: attachment; filename="test.html"' http://<modem-ip>/) and observe whether special characters or newline injection is reflected in the response without sanitizationAffected if The header value is echoed back without proper encoding or validation of CRLF/newline characters
The environment is affected if the device is a Telstra Smart Modem Gen 2 running firmware released up to January 2025, with its HTTP management interface exposed to network attackers who could inject arbitrary Content-Disposition header values.
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.
From vendor dataSince the vendor did not respond to early disclosure, network-level controls such as restricting access to the modem's management interface and implementing WAF rules to filter abnormal Content-Disposition headers are recommended as interim measures. Consider replacing the affected hardware if no firmware patch becomes available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0697 — 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-2025-0697 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