What is CVE-2014-9708?A medium-severity flaw in Appweb, explained.
CVE-2014-9708 is a medium-severity flaw (CVSS 5.0) in Appweb from Embedthis, published on 31 March 2015. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 56%. If you run an affected version, plan in the vendor’s fix.
Published 31 March 2015. Record last updated 12 April 2025. We keep this page's data up to date.
What is CVE-2014-9708? In plain terms.
It can be attacked from anywhere on the internet without logging in. If it works, the attacker can slow it down.
Embedthis Appweb before 4.6.6 and 5.x before 5.2.1 allows remote attackers to cause a denial of service (NULL pointer dereference) via a Range header with an empty value, as demonstrated by "Range: x=,".
What kind of flaw is it?
- CWE-476NULL Pointer Dereference
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- What an attacker getsCan slow it down
Severity vector: AV:N/AC:L/Au:N/C:N/I:N/A:P
Is CVE-2014-9708 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 56%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
CVE-2014-9708 scores 50. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2014-9708 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2014-9708? 134 products.
The published record lists 134 products from 3 vendors. Versions are shown as published: "before 4.6.6" means every version up to, but not including, 4.6.6. If you run one of these, check your version, then go to the fix below.
- Application
Appweb
by Embedthis
Affected versionsbefore 4.6.65.0.0 to before 5.2.1 - Operating system
Junos
by Juniper
Affected versions12.1x4612.1x46-d1012.1x46-d1512.1x46-d2012.1x46-d2512.1x46-d30 - Application
Enterprise Communications Broker
by Oracle
Affected versionsup to 2.0.0 - Hardware
Ex2200
by Juniper
Affected versionsversion not specified - Hardware
Ex2200-C
by Juniper
Affected versionsversion not specified - Hardware
Ex2200-Vc
by Juniper
Affected versionsversion not specified - Hardware
Ex2300
by Juniper
Affected versionsversion not specified - Hardware
Ex2300-24mp
by Juniper
Affected versionsversion not specified - Hardware
Ex2300-24p
by Juniper
Affected versionsversion not specified
How do I fix CVE-2014-9708? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
14 links- oss-security mailing list post, 28 Mar 2015 (opens in a new tab)openwall.com · 2015
- oss-security mailing list post, 6 Apr 2015 (opens in a new tab)openwall.com · 2015
- Cpujul2016 2881720 (opens in a new tab)oracle.com
- embedthis/appweb commit (opens in a new tab)github.com
- Appweb Web Server Denial Of Service (opens in a new tab)packetstormsecurity.com
- Fulldisclosure (opens in a new tab)seclists.org · 2015
Does CVE-2014-9708 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Embedthis Appweb before 4.6.6 and 5.x before 5.2.1 allows remote attackers to cause a denial of service (NULL pointer dereference) via a Range header with an...
- Matched to
- Appweb on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2014-9708 is a medium-severity flaw in Appweb from Embedthis, published on 31 March 2015. It can be attacked from anywhere on the internet without logging in. If it works, the attacker can slow it down.
It scores 5.0 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2014-9708 is 50 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 56%. That can change at any time, which is why we keep watching.
For Appweb from Embedthis: before 4.6.6, 5.0.0 to before 5.2.1. The record lists 134 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.