CVE-2014-2946
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 · uneditedCross-site request forgery (CSRF) vulnerability in api/sms/send-sms in the Web UI 11.010.06.01.858 on Huawei E303 modems with software 22.157.18.00.858 allows remote attackers to hijack the authentication of administrators for requests that perform API operations and send SMS messages via a request element in an XML document.
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 confidenceCSRF vulnerability in Huawei E303 modem's Web UI SMS API endpoint (api/sms/send-sms) allows remote attackers to send SMS messages by tricking authenticated administrators into visiting malicious pages. The API lacks anti-CSRF tokens, enabling attackers to hijack authenticated sessions for unauthorized SMS operations.
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= 11.010.06.01.858= 22.157.18.00.858= ch2e303smCVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 device modelAccess the modem's web interface or use AT commands to retrieve the product model identifier. Look for 'E303' or 'ch2e303sm' in the device information.Affected if The device model is Huawei E303 or ch2e303sm.
-
Check the modem firmware versionAccess the modem's admin web interface and navigate to the device information or status page. Alternatively, use the AT command 'AT+CGMR' to retrieve the firmware version.Affected if The firmware version equals 22.157.18.00.858.
-
Check the WebUI versionAccess the modem's web interface and locate the software or firmware version information, typically found in the settings, about, or system information section.Affected if The WebUI version equals 11.010.06.01.858.
-
Verify SMS API endpoint accessibilityAttempt to access the URL path '/api/sms/send-sms' on the modem's web interface using HTTP GET or POST. This endpoint is part of the Web UI SMS API.Affected if The endpoint responds and accepts SMS submission requests without requiring re-authentication for each request.
-
Check for CSRF token implementationSubmit a request to the /api/sms/send-sms endpoint and inspect whether the request requires a unique anti-CSRF token or session token that changes with each request. Compare this to the initial login response to see if tokens are generated per-session.Affected if The SMS API endpoint accepts requests without requiring a unique, dynamic CSRF token for each operation.
A user is affected if they are running a Huawei E303 modem with firmware version 22.157.18.00.858 and WebUI version 11.010.06.01.858, where the SMS API endpoint at /api/sms/send-sms lacks anti-CSRF token protection.
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 dataApply vendor firmware update if available; otherwise implement network segmentation to limit admin interface exposure and deploy CSRF tokens on the SMS API endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2946 — 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-2014-2946 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