DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Missouri Teachers’ Social Security numbers at risk on state agency’s website; state’s response is to shoot the messenger?

Posted on October 14, 2021 by Dissent

Josh Renaud reports:

The Social Security numbers of school teachers, administrators and counselors across Missouri were vulnerable to public exposure due to flaws on a website maintained by the state’s Department of Elementary and Secondary Education.

The Post-Dispatch discovered the vulnerability in a web application that allowed the public to search teacher certifications and credentials

Read more on St. Louis Post-Dispatch.

Now at this point, you’re probably asking the usual questions like “How many were potentially at risk?” “How long had this been a problem?” and “Is there any evidence that the data were accessed or downloaded for possible misuse?”  But while those are all reasonable questions, my question is ‘Why is the administration engaging in “Shoot the Messenger?’ and calling the reporter a “hacker?”

According to the Post-Dispatch’s report, in both a press release on the state’s site and a letter to educators, the state blamed the Post-Dispatch for discovering the vulnerability and referred to the reporter as a hacker.


Through a multi-step process, a hacker took the records of at least three educators, decoded the HTML source code, and viewed the social security number (SSN) of those specific educators.


The letter to educators replaced “hacker” with “individual.”

Sam Clancy of KSDK in Missouri seems to have picked up the state’s claims and KSDK headlines a story: “Hacker gets SSN, other information of 3 Missouri teachers in data breach.”

KSDK probably had no idea they were accusing another journalist of being a hacker.

But kudos to the St. Louis Post-Dispatch team that found the problem, confirmed it, and then responsibly disclosed it to the state.  I’m going to let their external counsel, attorney Joseph Martineau of Lewis Rice, have the last word here, although I note that Martineau seems to only use “hacker” in a criminal sense, whereas many hackers are whitehats and administrators:

“The reporter did the responsible thing by reporting his findings to DESE so that the state could act to prevent disclosure and misuse,” Martineau said in a written statement. “A hacker is someone who subverts computer security with malicious or criminal intent. Here, there was no breach of any firewall or security and certainly no malicious intent.

“For DESE to deflect its failures by referring to this as ‘hacking’ is unfounded. Thankfully, these failures were discovered.”

DESE:  we’ll just wait over here for you to apologize for attempting to deflect blame to the reporter who discovered your security problem and who worked with their team to responsibly disclose it to you.

Update: The state seems to be doubling down on accusing the reporter and the press of illegal conduct. You can watch the Governor’s press conference/statement on YouTube.


Related:

  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
Category: Commentaries and AnalysesEducation SectorExposureGovernment SectorU.S.

Post navigation

← Update: Missouri Delta Medical Center acknowledges ransomware incident
Acer India hacked — again? →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Maryland Privacy Crackdown Raises Bar for Disclosure Compliance
  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.