An issue was discovered on Securifi Almond, Almond+, and Almond 2015 devices with firmware AL-R096. The device provides a user with the capability of setting name for wireless network. These values are stored by the device in NVRAM (Non-volatile RAM). It seems that the POST parameters passed in this request to set up names on the device do not have a string length check on them. This allows an attacker to send a large payload in the "mssid_1" POST parameter. The device also allows a user to view the name of the Wifi Network set by the user. While processing this request, the device calls a function named "getCfgToHTML" at address 0x004268A8 which retrieves the value set earlier by "mssid_1" parameter as SSID2 and this value then results in overflowing the stack set up for this function and allows an attacker to control $ra register value on the stack which allows an attacker to control the device by executing a payload of an attacker's choice. If the firmware version AL-R096 is dissected using binwalk tool, we obtain a cpio-root archive which contains the filesystem set up on the device that contains all the binaries. The binary "goahead" is the one that has the vulnerable function that recieves the values sent by the POST request. If we open this binary in IDA-pro we will notice that this follows a MIPS little endian format. The function sub_00420F38 in IDA pro is identified to be receiving the values sent in the POST parameter "mssid_1" at address 0x0042BA00 and then sets in the NVRAM at address 0x0042C314. The value is later retrieved in the function "getCfgToHTML" at address 0x00426924 and this results in overflowing the buffer due to "strcat" function that is utilized by this function.
CVE-2017-8335
Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2022-05-24. NVD baseline CVSS 8.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 8.0
- EG Score
- 8.0HIGHmedium confidence
- EG Risk
- 41EG Risk 41/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity80% × 45%Exploitation2% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 2.1%
- EPSS %ILE
- 80th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
June 18, 2019
Last Modified
November 21, 2024
Advisory Details (3)
Auto-updated Sep 20, 2026IoT_vulnerabilities/Securifi_Almond_plus_sec_issues.pdf at master · ethanhunnt/IoT_vulnerabilities · GitHub
https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Securifi_Almond_plus_sec_issues.pdfLocked Out | Packet Storm
http://packetstormsecurity.com/files/153227/Securifi-Almond-2015-Buffer-Overflow-Command-Injection-XSS-CSRF.htmlWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 151 total refreshes for this CVE.
- 2026-10-05 17:39 UTCEPSS rescore
- 2026-10-04 23:18 UTCEPSS rescore
- 2026-10-03 14:21 UTCEPSS rescore
- 2026-10-03 14:21 UTCEPSS rescore
- 2026-09-30 14:59 UTCEPSS rescore
- 2026-09-30 09:41 UTCEG score recompute
- 2026-09-28 13:45 UTCEPSS rescore
- 2026-09-27 13:40 UTCEPSS rescore
- 2026-09-27 13:40 UTCEPSS rescore
- 2026-09-26 15:53 UTCEPSS rescore
- 2026-09-26 00:19 UTCEPSS rescore
- 2026-09-24 13:59 UTCEPSS rescore
- 2026-09-23 13:42 UTCEPSS rescore
- 2026-09-21 20:27 UTCEPSS rescore
- 2026-09-19 15:36 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-15 03:05 UTCEPSS rescore
- 2026-09-12 14:56 UTCEPSS rescore
- 2026-09-11 09:31 UTCEPSS rescore
- 2026-09-07 15:56 UTCEPSS rescore
- 2026-09-05 15:24 UTCEPSS rescore
- 2026-09-04 13:56 UTCEPSS rescore
- 2026-09-04 05:02 UTCEPSS rescore
- 2026-09-02 14:07 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-02 14:07 UTCEPSS rescore
- 2026-09-01 03:31 UTCEPSS rescore
- 2026-08-30 19:13 UTCEPSS rescore
- 2026-08-28 21:36 UTCEPSS rescore
- 2026-08-27 14:21 UTCEPSS rescore
- 2026-08-26 14:41 UTCEPSS rescore
- 2026-08-25 13:44 UTCEPSS rescore
- 2026-08-23 00:14 UTCEPSS rescore
- 2026-08-21 23:44 UTCEPSS rescore
- 2026-08-19 16:59 UTCEPSS rescore
- 2026-08-18 13:43 UTCEPSS rescore
- 2026-08-16 14:51 UTCEPSS rescore
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-12 13:46 UTCEPSS rescore
- 2026-08-09 13:42 UTCEPSS rescore
- 2026-08-08 16:32 UTCEPSS rescore
- 2026-08-07 16:22 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-05 19:13 UTCEPSS rescore
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-08-01 04:12 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-30 01:26 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:30 UTCEG score recompute
- 2026-07-22 22:10 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 10:01 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:55 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-11 08:24 UTCEPSS rescore
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-08 15:11 UTCEPSS rescore
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-02 16:54 UTCEPSS rescore
- 2026-07-01 15:03 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-29 14:03 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:06 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-23 21:30 UTCEPSS rescore
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2017-8335?
When was CVE-2017-8335 disclosed?
Is CVE-2017-8335 actively exploited?
What is the CVSS score of CVE-2017-8335?
How do I remediate CVE-2017-8335?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2017-8335
Is Your Infrastructure Affected by CVE-2017-8335?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.