CVE-2015-1187: The ping tool in multiple D-Link and TRENDnet devices allow remote attackers to execute arbitrary code via the ping_addr parameter to…
Noroxi assessment
Priority: Now (action score 94/100)
- CISA has confirmed exploitation in the wild (Mar 25, 2022). Remediation deadline for US federal agencies: Apr 15, 2022.
- A ready-made attack module is public (Metasploit); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 82.6% (FIRST EPSS); higher than 99.6% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Patch today or shut off access. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
The ping tool in multiple D-Link and TRENDnet devices allow remote attackers to execute arbitrary code via the ping_addr parameter to ping.ccp.
- Published
- Sep 21, 2017
- Updated
- Jun 16, 2026
- EPSS
- 82.6% · 99th percentile
- CWE
- CWE-287
Report tools
Action score
94
Patch today or shut off access.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 25 / 30 · 82.6%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Mar 25, 2022. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Apr 15, 2022.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| trendnet | tew-731br firmware | cpe:2.3:o:trendnet:tew-731br_firmware |
| trendnet | tew-731br | cpe:2.3:h:trendnet:tew-731br |
| trendnet | tew-651br firmware | cpe:2.3:o:trendnet:tew-651br_firmware |
| trendnet | tew-651br | cpe:2.3:h:trendnet:tew-651br |
| trendnet | tew-652br firmware | cpe:2.3:o:trendnet:tew-652br_firmware |
| trendnet | tew-652br | cpe:2.3:h:trendnet:tew-652br |
| trendnet | tew-711br firmware | cpe:2.3:o:trendnet:tew-711br_firmware |
| trendnet | tew-711br | cpe:2.3:h:trendnet:tew-711br |
| trendnet | tew-810dr firmware | cpe:2.3:o:trendnet:tew-810dr_firmware |
| trendnet | tew-810dr | cpe:2.3:h:trendnet:tew-810dr |
| trendnet | tew-813dru firmware | cpe:2.3:o:trendnet:tew-813dru_firmware |
| trendnet | tew-813dru | cpe:2.3:h:trendnet:tew-813dru |
and 18 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dlink dir-626l firmware1.04
- dlink dir-636l firmware1.04
- dlink dir-651 firmware1.10na
- dlink dir-808l firmware1.03
- dlink dir-810l firmware1.01
- dlink dir-810l firmware2.02
- dlink dir-820l firmware1.02
- dlink dir-820l firmware1.05
+10 more rows
- dlink dir-820l firmware2.01
- dlink dir-826l firmware1.00
- dlink dir-830l firmware1.00
- dlink dir-836l firmware1.01
- trendnet tew-651br firmwareall versions
- trendnet tew-652br firmwareall versions
- trendnet tew-711br firmware1.00
- trendnet tew-731br firmware2.01
- trendnet tew-810dr firmware1.00
- trendnet tew-813dru firmware1.00
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Exploit-DB entry ×1
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2015-02-26 |
| Metasploit module | exploit/linux/http/multi_ncc_ping_execD-Link/TRENDnet NCC Service Command Injectionexploit | 2015-02-26 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-06-30 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-939 d
- Metasploit-939 d
- Published
- CISA KEV+1645 d
- TodayNov 16, 2026+3343 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.