From: Antti Palosaari <crope@iki.fi>
To: LMML <linux-media@vger.kernel.org>
Subject: Fwd: [SE-2011-01] PoC code for digital SAT TV research released
Date: Fri, 22 Mar 2013 19:31:37 +0200 [thread overview]
Message-ID: <514C9579.5040309@iki.fi> (raw)
In-Reply-To: <514B0B81.2090408@security-explorations.com>
Could be interesting reading for DTV hackers!
regards
Antti
-------- Original Message --------
Subject: [SE-2011-01] PoC code for digital SAT TV research released
Date: Thu, 21 Mar 2013 14:30:41 +0100
From: Security Explorations <contact@security-explorations.com>
To: full-disclosure@lists.grok.org.uk, bugtraq@securityfocus.com
Hello All,
Last year, we disclosed information pertaining to security issues
discovered as a result of our digital satellite TV research [1].
It's been over a year and we haven't received [2] information with
respect to the status and impact of the vulnerabilities found in:
- digital satellite TV set-top-boxes produced by Advanced Digital
Broadcast [3],
- DVB / MPEG chipsets manufactured by STMicroelectronics [4].
We haven't received important information from Conax AS [5] either.
This in particular concerns a final security level assigned by the
company to set-top boxes and secure DVB chipsets evaluated as part
of Conax security / evaluation process. Conax "rigorous evaluation
and testing regime" [6] missed serious security vulnerabilities
potentially affecting 540 millions [7] of DVB / MPEG chipsets.
Today, a new digital satellite TV platform starts in Poland. It is
called NC+ [8] and it is apparently based on equipment / technology
coming from several vendors, which were affected by security issues
found as part of SE-2011-01 project.
We take the above as a perfect opportunity to verify whether these
vendors had learned anything from the results of our 1.5 years long
research. We assume that they have and that in particular:
- all of security issues discovered as part of our SE-2011-01 project
have been properly resolved,
- new equipment is considerably harder to hack or use for any SAT TV
piracy purposes.
We decided to release our Proof of Concept code developed as part of
SE-2011-01 project [9]. Its source code is is available for download
from the following location:
http://www.security-explorations.com/en/SE-2011-01-details.html
We believe that the security community and professionals involved in
a development of digital satellite TV ecosystems should benefit the
most from the release of our Proof of Concept code.
Thank you.
Best Regards,
Adam Gowdiak
---------------------------------------------
Security Explorations
http://www.security-explorations.com
"We bring security research to the new level"
---------------------------------------------
References:
[1] SE-2011-01 Security weaknesses in a digital satellite TV platform
http://www.security-explorations.com/en/SE-2011-01.html
[2] SE-2011-01 Vendors status
http://www.security-explorations.com/en/SE-2011-01-status.html
[3] Advanced Digital Broadcast
http://www.adbglobal.com
[4] STMicroelectronics
http://www.st.com
[5] Conax AS
http://www.conax.com
[6] Conax Security Evaluation Scheme
http://www.conax.com/products-solutions/advanced-security-features/security-evaluation-scheme/
[7] Multimedia Convergence & ACCI Sector Overview, Philippe Lambinet,
STMicroelectronics
http://www.st.com/internet/com/CORPORATE_RESOURCES/COMPANY/COMPANY_PRESENTATION/5_mult_conv_acci_lambinet.pdf
[8] NC+ Digital Satellite TV Plaform
http://ncplus.pl/
[9] SE-2011-01 Proof of Concept Code (technical information)
http://www.security-explorations.com/en/SE-2011-01-poc.html
parent reply other threads:[~2013-03-22 17:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <514B0B81.2090408@security-explorations.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=514C9579.5040309@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.