aboutsummaryrefslogtreecommitdiffstats
path: root/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md
diff options
context:
space:
mode:
Diffstat (limited to 'markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md')
-rw-r--r--markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md b/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md
index 532bf26..12c0573 100644
--- a/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md
+++ b/markdown/2012_09_replicant-2-3-0005-images-fixing-the-ussd-vulnerability.md
@@ -12,7 +12,7 @@ very powerful. This is mostly the case of vendor-specific USSD codes (that are
not included in Replicant), which could erase the phone's user data.
What's also problematic about this is that web pages can trigger such intents
-(through an iframe with the `tel:` prefix for instance).
+(through an iframe with the `tel:` prefix for instance).
Since this vulnerability was present in our Replicant images (although the
damage was reduced as we don't include vendor-specific USSD codes), we decided
to include the fix in our code base and release new images. That's nearly the