Data: CASIE
Negative Trigger
from
security
researchers
involving
the
company
’
s
routers
.
The
latest
incident
arose
after
Silesian
University
of
Technology
researcher
Błazej
Adamczyk
contacted
Vulnerability-related.DiscoverVulnerability
D-Link
last
May
about
three
vulnerabilities
affecting
Vulnerability-related.DiscoverVulnerability
eight
router
models
.
Following
the warning
Vulnerability-related.DiscoverVulnerability
,
D-Link
patched
Vulnerability-related.PatchVulnerability
two
of
the
affected
routers
,
but
did
not
initially
reveal
Vulnerability-related.DiscoverVulnerability
how
it
would
proceed
for
the
remaining
six
models
.
After
further
prompting
Vulnerability-related.DiscoverVulnerability
from
Adamczyk
,
D-Link
revealed
Vulnerability-related.DiscoverVulnerability
that
the
remaining
six
routers
would not get
Vulnerability-related.PatchVulnerability
a
security
patch
because
they
were
considered
end-of-life
models
,
leaving
affected
owners
out
in
the
cold
.
“
The
D-Link
models
affected
Vulnerability-related.DiscoverVulnerability
are
the
DWR-116
,
DWR-140L
,
DWR-512
,
DWR-640L
,
DWR-712
,
DWR-912
,
DWR-921
,
and
DWR-111
,
six
of
which
date
from
2013
,
with
the
DIR-640L
first appearing
Vulnerability-related.DiscoverVulnerability
in
2012
and
the
DWR-111
in
2014
,
”
Naked
Security
reported
.
Though
these
are
not
current
models
in
D-Link
’
s
portfolio
,
many
of
the
listed
models
are
still
likely
to
be
in
use
.
As
a
result
of
this
impasse
,
Adamczyk
released details
Vulnerability-related.DiscoverVulnerability
about
the
security
flaws
,
following
responsible
security
protocols
after
giving
D-Link
notice
and
the
opportunity
to
address
Vulnerability-related.PatchVulnerability
the
issues
.
Of
significance
is
that
this
is
the
second
time
in
about
a
year
that
D-Link
has failed to address
Vulnerability-related.PatchVulnerability
security
vulnerabilities
affecting
Vulnerability-related.DiscoverVulnerability
its
products
after
being notified
Vulnerability-related.DiscoverVulnerability
by
researchers
.
The
security
researcher
noted
Vulnerability-related.DiscoverVulnerability
that
the
new
flaw
arose
Vulnerability-related.DiscoverVulnerability
after
D-Link
reported
that
it
had fixed
Vulnerability-related.PatchVulnerability
a
prior
security
flaw
.
Also
known
as
“
directory
traversal
”
or
“
dot
dot
slash
”
attacks
,
these
flaws
allow
a
malicious
attacker
to
gain
access
to
system
files
with
a
simple
HTTP
request
.
Despite
D-Link
’
s
spotty
history
with
supporting
older
router
models
,
the
manufacturer
is
not
alone
in
leaving
routers
unpatched
Vulnerability-related.PatchVulnerability
.
The
American
Consumer
Institute
reported
Vulnerability-related.DiscoverVulnerability
that
of
the
186
routers
it
had
tested
,
155
contained
Vulnerability-related.DiscoverVulnerability
firmware
vulnerabilities
.
In
total
,
ACI
discovered
Vulnerability-related.DiscoverVulnerability
more
than
32,000
known
vulnerabilities
in
its
study
.
“
Our
analysis
shows
that
,
on
average
,
routers
contained
Vulnerability-related.DiscoverVulnerability
12
critical
vulnerabilities
and
36
high-risk
vulnerabilities
,
across
the
entire
sample
,
”
ACI
noted
in
its
report
.
“
The
most
common
vulnerabilities
were
medium-risk
,
with
an
average
of
103
vulnerabilities
per
router.
”
For
shoppers
who
are
in
the
market
for
a
new
router
,
it
’
s
probably
best
to
also
check
with
the
manufacturer
to
see
what
the
supported
lifespan
of
the
router
is
.
If
the
router
is
nearing
its
end
of
life
,
as
in
the
case
illustrated
here
,
you
may
not
get
Vulnerability-related.PatchVulnerability
patches
,
regardless
of
how
serious
a
security
vulnerability
may
be
.
If
you
have
an
older
router
,
you
may
want
to
consider
checking
out
our
guide
for
the
best
router
options
before
you
decide
to
upgrade
.
A
popular
version
of
the
open
source
Magento
ecommerce
platform
is vulnerable
Vulnerability-related.DiscoverVulnerability
to
a
zero-day
remote
code
execution
vulnerability
,
putting
as
many
as
200,000
online
retailers
at
risk
.
The
warning
comes
from
security
firm
DefenseCode
,
which
found
Vulnerability-related.DiscoverVulnerability
and
originally
reported
Vulnerability-related.DiscoverVulnerability
the
vulnerability
to
Magento
in
November
.
“
During
the
security
audit
of
Magento
Community
Edition
,
a
high
risk
vulnerability
was discovered
Vulnerability-related.DiscoverVulnerability
that
could
lead
to
remote
code
execution
and
thus
the
complete
system
compromise
including
the
database
containing
sensitive
customer
information
such
as
stored
credit
card
numbers
and
other
payment
information
,
”
DefenseCode
wrote
in
a
technical
description
of
its
discovery
(
PDF
)
posted
Wednesday
.
According
Bosko
Stankovic
,
information
security
engineer
at
DefenseCode
,
despite
repeated
efforts
to
notify
Vulnerability-related.DiscoverVulnerability
Magento
,
which
began
in
November
2016
,
the
vulnerability
remains
unpatched
Vulnerability-related.PatchVulnerability
despite
four
version
updates
since
the disclosure
Vulnerability-related.DiscoverVulnerability
.
DefenseCode
did
not
examine
Magento
Enterprise
,
the
commercial
version
of
the
platform
,
but
warns
both
share
the
same
underlying
vulnerable
code
.
“
We
’
re
unsure
if
this
vulnerability
is
actively
being exploited
Vulnerability-related.DiscoverVulnerability
in
the
wild
,
but
since
the
vulnerability
has been unpatched
Vulnerability-related.PatchVulnerability
for
so
long
it
provides
a
window
of
opportunity
for
potential
hackers
,
”
Stankovic
said
.
Magento
confirmed the existence
Vulnerability-related.DiscoverVulnerability
of
the
flaw
in
a
brief
statement
to
Threatpost
and
said
it
was
investigating
.
“
We
have been actively investigating
Vulnerability-related.DiscoverVulnerability
the
root
cause
of
the
reported
issue
and
are
not
aware
of
any
attacks
in
the
wild
.
We
will be addressing
Vulnerability-related.PatchVulnerability
the
issue
in
our
next
patch
release
and
continue
to
consistently
work
to
improve
our
assurance
processes
,
”
Magento
said
in
a
statement
.
Yesterday
,
Threatpost
reported
Vulnerability-related.DiscoverVulnerability
a
story
about
a
remote
code
execution
vulnerability
with
Magento
2
Enterprise
and
Community
software
.
Magento
is
committed
to
delivering
superior
security
to
clients
and
has been actively investigating
Vulnerability-related.DiscoverVulnerability
the
root
cause
of
the
reported
issue
.
We
are
not
aware
of
any
attacks
in
the
wild
.
Admin
access
is
required
to
execute
the
exploit
,
so
as
always
,
we
encourage
you
to
follow
best
practices
to
keep
your
Admin
secure
.
In
addition
,
this
vulnerability
will be addressed
Vulnerability-related.PatchVulnerability
in
our next release
Vulnerability-related.PatchVulnerability
targeted
for
early
May
.
Until
then
,
we
recommend
enforcing
the
use
of
“
Add
Secret
Key
to
URLs
”
to
mitigate
potential
attacks
.