Skip to content

Instantly share code, notes, and snippets.

@azizur
Created September 23, 2016 22:02
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save azizur/40003633b56306f1f871602b09e51f18 to your computer and use it in GitHub Desktop.
Save azizur/40003633b56306f1f871602b09e51f18 to your computer and use it in GitHub Desktop.
Producteev User - Notice of Data Breach
Delivered-To: EMAIL_ADDRESS_REMOVED
Received: by 10.80.165.111 with SMTP id z44csp568758edb;
Fri, 23 Sep 2016 14:34:47 -0700 (PDT)
X-Received: by 10.36.111.199 with SMTP id x190mr5908699itb.61.1474666487030;
Fri, 23 Sep 2016 14:34:47 -0700 (PDT)
Return-Path: <bounces+256423-f6c7-USER_REMOVED=DOAMIN_REMOVED@emailapp.producteev.com>
Received: from o1.emailapp.producteev.com (o1.emailapp.producteev.com. [50.31.50.134])
by mx.google.com with ESMTPS id j185si11543537iof.9.2016.09.23.14.34.46
for <EMAIL_ADDRESS_REMOVED>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 23 Sep 2016 14:34:47 -0700 (PDT)
Received-SPF: pass (google.com: domain of bounces+256423-f6c7-USER_REMOVED=DOAMIN_REMOVED@emailapp.producteev.com designates 50.31.50.134 as permitted sender) client-ip=50.31.50.134;
Authentication-Results: mx.google.com;
dkim=pass header.i=@emailapp.producteev.com;
spf=pass (google.com: domain of bounces+256423-f6c7-USER_REMOVED=DOAMIN_REMOVED@emailapp.producteev.com designates 50.31.50.134 as permitted sender) smtp.mailfrom=bounces+256423-f6c7-USER_REMOVED=DOAMIN_REMOVED@emailapp.producteev.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=emailapp.producteev.com; h=content-type:from:mime-version:reply-to:subject:to; s=smtpapi; bh=aIh2aL4345bod6uJS8q8247CPJg=; b=gkIlhJJpGuhC9SN8crQ9I4/zEZ+cD hKwIZ47bQY68du/+B3Kuz++dadIiQybIdjRJ3YdqpJKL1l77fr+u52IR1yv8DK+h iK/HF6hCBuUmcZE+CYIP4DRAl094RAPpVgZjgmsGPzjS0eX/ppdVdvX59dGa7NNN +wQKhU3Yu66sQw=
Received: by filter0793p1mdw1.sendgrid.net with SMTP id filter0793p1mdw1.25347.57E59FC54
2016-09-23 21:33:57.036404441 +0000 UTC
Received: from MjU2NDIz (o16789125x253.outbound-mail.sendgrid.net [167.89.125.253]) by ismtpd0004p1iad1.sendgrid.net (SG) with HTTP id T2YvpCmnRhuangKoGeRg0g for <support@producteev.io>; Fri, 23 Sep 2016 21:33:56.911 +0000 (UTC)
Content-Type: multipart/alternative; boundary=35d6f4c8ec8ea5a38a6c04f929b59239fe4811247cae4877ee9e17cbe9de
Date: Fri, 23 Sep 2016 21:33:56 +0000
From: Producteev Team <support@producteev.io>
Mime-Version: 1.0
Reply-to: no-reply@producteev.io
Subject: Notice
To: EMAIL_ADDRESS_REMOVED
Message-ID: <T2YvpCmnRhuangKoGeRg0g@ismtpd0004p1iad1.sendgrid.net>
X-SG-EID: Ia9l3LyAJzh7OzNzfS16MFkjK47AKrm2r9Ihe5scQpUxn8NpetKpJSUnbf7vme4JAvXKjRxGXlWJRF aQKY9rAQlrit/q6/X0ODms+6soWiaIqg0ioxZyrQHvLW8AZc6YJiuP3hT/rrDV3uWZPDxx+mUwomdD T30H5j9kVqKA8duKEGTt8IaEXGKYNxb3/FfvVGvHonStydI+DlkMGlZMPAGbPZ11xxFheRA59pZqyA g=
X-SG-ID: Z2FxZazunBjVeNuNdzHDqrF8mxuCpi0krmont6YQrP1+FvTnoS5rwHQ4eMqC8r40D212gAN6Osz1LB Guckn57TM6ACI8SVGTnS5uwtfXuANpgHutwng+1bk35KuR1p+VVFLRUwp93A9LhKAkS6puR+ePH2pS ydzErLCufrgE5NTxFWHREA4WAK7YmI2HDh5Y
--35d6f4c8ec8ea5a38a6c04f929b59239fe4811247cae4877ee9e17cbe9de
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Mime-Version: 1.0
Notice of Data Breach
Dear Producteev User:=20
What happened?
We want to inform you of an issue involving your Producteev username (i.e. =
your email address) and password. We learned on August 24 that your Product=
eev username and password had been held in a file outside our normal encryp=
tion procedures, and we believe that this file was potentially accessed by =
an unauthorized third party. We cannot confirm that your username or passwo=
rd was compromised, but we are notifying you so that you may=C2=A0take prot=
ective action.=20
What information was involved?
Only your username and password was held in the file. We have not experienc=
ed any unusual login activity as a result of this incident, but if an unaut=
horized party obtained your credentials and logged into your Producteev acc=
ount, he or she could access your name, your tasks, and other information s=
tored in your account.
Although Producteev collects additional information from users with paid ac=
counts, that information is stored separately and was not implicated in thi=
s incident.=20
What are we doing?
Upon discovery, the Producteev team took immediate steps to investigate and=
seek to remedy the issue. The team has discovered the cause of the issue a=
nd remediated the vulnerability causing it.=C2=A0 As detailed below, we are=
requiring that all users change their passwords.
What can you do?
As a safety precaution, we have cleared your current password and are requi=
ring password changes in order for users to access their Producteev account=
s. When logging into Producteev.com, you will be required to change your pa=
ssword. In addition, within the Producteev app, you can change your passwor=
d at any time by going into your account settings and requesting to change =
passcode.
We also recommend that you change the password on any other account where y=
ou use the same password potentially compromised in this incident.=20
For More Information
If you have additional questions, please write to us at support@producteev.=
io.
On behalf of Producteev, we regret any inconvenience this may cause you.
Sincerely,=20
The Producteev Team
Click Here to Unsubscribe mailto:support@producteev.com
--35d6f4c8ec8ea5a38a6c04f929b59239fe4811247cae4877ee9e17cbe9de
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8
Mime-Version: 1.0
<html>
<head>
=09<title></title>
</head>
<body>
<p style=3D"margin: 25px;"><strong>Notice of Data Breach</strong></p>
<p style=3D"margin: 25px;"><span style=3D"font-size: 11.0pt;">Dear Producte=
ev User: </span></p>
<p style=3D"margin: 25px;"><strong><span style=3D"font-size: 11.0pt;">What =
happened?</span></strong><br />
<span style=3D"font-size: 11.0pt;">We want to inform you of an issue involv=
ing your Producteev username (i.e. your email address) and password. We lea=
rned on August 24 that your Producteev username and password had been held =
in a file outside our normal encryption procedures, and we believe that thi=
s file was potentially accessed by an unauthorized third party. We cannot c=
onfirm that your username or password was compromised, but we are notifying=
you so that you may&nbsp;take protective action. </span></p>
<p style=3D"margin: 25px;"><strong><span style=3D"font-size: 11.0pt;">What =
information was involved?</span></strong><br />
<span style=3D"font-size: 11.0pt;">Only your username and password was held=
in the file. We have not experienced any unusual login activity as a resul=
t of this incident, but if an unauthorized party obtained your credentials =
and logged into your Producteev account, he or she could access your name, =
your tasks, and other information stored in your account.</span></p>
<p style=3D"margin: 25px;"><span style=3D"font-size: 11.0pt;">Although Prod=
ucteev collects additional information from users with paid accounts, that =
information is stored separately and was not implicated in this incident. <=
/span></p>
<p style=3D"margin: 25px;"><strong><span style=3D"font-size: 11.0pt;">What =
are we doing?</span></strong><br />
<span style=3D"font-size: 11.0pt;">Upon discovery, the Producteev team took=
immediate steps to investigate and seek to remedy the issue. The team has =
discovered the cause of the issue and remediated the vulnerability causing =
it.&nbsp; As detailed below, we are requiring that all users change their p=
asswords.</span></p>
<p style=3D"margin: 25px;"><strong><span style=3D"font-size: 11.0pt;">What =
can you do?</span></strong><br />
<span style=3D"font-size: 11.0pt;">As a safety precaution, we have cleared =
your current password and are requiring password changes in order for users=
to access their Producteev accounts. When logging into Producteev.com, you=
will be required to change your password. In addition, within the Producte=
ev app, you can change your password at any time by going into your account=
settings and requesting to change passcode.</span></p>
<p style=3D"margin: 25px;"><span style=3D"font-size: 11.0pt;">We also recom=
mend that you change the password on any other account where you use the sa=
me password potentially compromised in this incident. </span></p>
<p style=3D"margin: 25px;"><strong><span style=3D"font-size: 11.0pt;">For M=
ore Information</span></strong><br />
<span style=3D"font-size: 11.0pt;">If you have additional questions, please=
write to us at support@producteev.io.</span></p>
<p style=3D"margin: 25px;"><span style=3D"font-size: 11.0pt;">On behalf of =
Producteev, we regret any inconvenience this may cause you.</span></p>
<p style=3D"margin: 25px;"><span style=3D"font-size: 11.0pt;">Sincerely, </=
span></p>
<p style=3D"margin: 25px;"><span style=3D"font-size: 11.0pt;">The Productee=
v Team</span></p>
<p style=3D"margin: 25px;">&nbsp;</p>
<p style=3D"margin: 25px;">&nbsp;</p>
<p style=3D"margin: 25px;">&nbsp;</p>
<p style=3D"margin: 25px;">&nbsp;</p>
<p style=3D"margin: 25px;">&nbsp;</p>
<div><span style=3D"font-size:8px;"><a clicktracking=3Doff href=3D"mailto:s=
upport@producteev.com">Click Here to Unsubscribe</a></span></div>
<img src=3D"http://emailapp.producteev.com/wf/open?upn=3DurAyTJLI-2B6Xjvy31=
onDw9zagyvhugRAJgO-2BNL12gWkBmBi9FjUabpEp6FyY07MBUECjPKCLCYPPxqEopypH-2BI7v=
HuwmmVwemzaa5lVNeAlD6Yw-2F-2B5C9j6eEviVhGw5tnqCJbL-2BMvdL9UqkOUYHV0ymWfmmLN=
TjIct1Vb7o6QapfI5QElzhHasaAf1Gfoh7b7TskbOkjCcUhfiIr-2B9IGfrhufQuHF26VGsKaB3=
BRFLL7yXvFahcMfgZ-2F1Q6sA4cG5Z-2BFe96ro-2BdKIrLeI2ADXjzQsYV646FRto8hQz7hRn-=
2BALBRUgo3ZPBpntqYJWuxZ-2B4-2F88gpr-2FZ49saT18W-2F4JRDjfJVTZ3MLHlb65F1G9501=
Kv9ybwlOEnFQhvFF0r7tyeZzxppVG6Fts-2B-2B9pDmLtS-2BHiAUY3JNtH7unr7GHNKKo-3D" =
alt=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"height:1px !importa=
nt;width:1px !important;border-width:0 !important;margin-top:0 !important;m=
argin-bottom:0 !important;margin-right:0 !important;margin-left:0 !importan=
t;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !imp=
ortant;padding-left:0 !important;"/>
</body>
</html>
--35d6f4c8ec8ea5a38a6c04f929b59239fe4811247cae4877ee9e17cbe9de--
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment