HackingEducationEducationVulnerability ExploitSupply Chain (3P Vendor)Customer Data InvolvedIdentity (basic)CredentialsLowContained

Red Bluff High School

bd_906c381b031c617b · schema v1 · pii pii-v1

Severity

Low

Discovered

May 3, 2020

Filed

Jun 29, 2020

To disclose

8 weeks

Affected

Not disclosed

Confidence

65%

Full breach record for Red Bluff High School →

Red Bluff Joint Union High School District notified parents that an unauthorized individual exploited a vulnerability in the Aeries Student Information System software. The exploit occurred in late November 2019, but the District learned of the potential access on May 3, 2020, and confirmed access on May 6, 2020. Affected data included parent/student names, addresses, phone numbers, emails, and hashed passwords. The District installed the software patch and recommended password changes.

J jump to incidentP pin to compareR raw source

California clockDiscovered May 3, 2020 → Notified May 6, 20203d ✓ CA 60-day OK8 weeks discovery → filing

Incident timeline

undetected · 184 days

discovery → filing · 8 weeks / 57 days

Nov 1, 2019

Begins

May 3, 2020

Discovered

Jun 29, 2020

Filed

vs. sector median

on median

Part of Aeries supply-chain incident (2020) — a supply-chain cascade affecting multiple organizations.View cascade →

Tracked as a single-filing incident — the only disclosure on record for this event so far.ConfirmedView incident

Name: Red Bluff High School
norm: red bluff high school
Domain: rbhs.rbhsd.org

Name: Red Bluff High School
norm: red bluff high school
Domain: rbhs.rbhsd.org
Industry: Educationllm

Discovered: May 3, 2020
Breach occurred: Nov 1, 2019 – Nov 30, 2019
Undetected for: 184 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 6, 2020
Affected individuals: Not disclosed
Data types: Identity (basic)Credentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing Application
Threat actor: External
Third party: via Aeries
Initial access: exploit_public_facing

During the incident: Conducted our own investigation
Law enforcement launched an investigation to identify the person responsible
Recommending all account holders whose accounts were involved to change their passwords
Changes made: Installed the software patch that Aeries made available to remedy the vulnerability
Reviewing our existing policies and procedures to mitigate any risk associated with this incident and to better prevent future incidents
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 8 weeks(57 days from discovery to filing)
Compliance flags: CA 60-day OK · 3d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.
Clock breakdown: Statute Window Elapsed Threshold Status
California
Discovered: May 3, 2020
→ Notified: May 6, 2020
3d 60 days (analyst band, pre-2026 discoveries) CA 60-day OK

Statute	Window	Elapsed	Threshold	Status
California	Discovered: May 3, 2020 → Notified: May 6, 2020	3d	60 days (analyst band, pre-2026 discoveries)	CA 60-day OK

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-191519
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jun 29, 2020
Raw hash: bf9fc5d98fb65a7cf9b983d637b8fe34729ea42a4c1f1bddac916d3f2bc7d220

Reporting entityRed Bluff High School

Victim entityRed Bluff High School

Incidentdiscovered May 3, 2020

Stated responseConducted our own investigation

ComplianceCA 60-day OK

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov