UK Government Exposes Sensitive Data Due To Security Flaws
A security researcher found over 100 vulnerabilities in UK government code, putting sensitive data at risk. The flaws were caused by poor cyber hygiene and neglect of technology maintenance.
Original reporting · wired.com
Original: “Security Flaws Across UK Government Sites Exposed ‘God-Tier’ Information”
Read “Security Flaws Across UK Government Sites Exposed ‘God-Tier’ Information” at WIRED AI →
How this was written. GDS wrote this article with a language model from WIRED AI’s reporting (model: @cf/meta/llama-3.3-70b-instruct-fp8-fast); it describes that reporting rather than adding to it. The original, linked above, is the full story.
Key points from WIRED AI’s report
- A security researcher found over 100 vulnerabilities in UK government code, putting sensitive data at risk due to poor cyber hygiene.
- The vulnerabilities were caused by neglect of technology maintenance and internal housekeeping failures when using public tools.
- The affected organizations have addressed the issues, but the incident highlights the need for improved cyber hygiene and maintenance practices within the UK government's technology estate.
- The discovery has sparked arguments about the practice of publishing source code in the open, with some organizations transitioning away from open source code due to security concerns.
- The issue is not solely related to open source security concerns, but rather a failure to follow good process and maintain technology estate.
The UK government's practice of openly publishing code produced with public money has been in place for around a decade, aiming to promote transparency and cost efficiency. According to WIRED AI, this approach has been adopted by various departments, including the Department of Health and Social Care and the Home Office, as well as local authorities. However, funding constraints have led to neglect in maintaining and improving the technology estate, resulting in security vulnerabilities.
A security researcher, Chris Nesbitt-Smith, discovered the vulnerabilities using consumer-grade AI models on a laptop, indicating that the issues could have been identified through routine IT health checks. The researcher found that the flaws were not sophisticated, but rather basic mistakes, with Nesbitt-Smith describing them as 'daft stuff'. WIRED AI reported that the vulnerabilities were found in over 100 publicly available UK government codebases.
One of the most serious cases involved the Planning Inspectorate, which handles land-use matters across England. The agency accidentally committed login credentials to a public repository, GitHub, and failed to fully remove them, compromising sensitive data. The credentials would have given 'god-tier' read and write access to all SharePoint sites and private employee OneDrive accounts, including HR records.
The Planning Inspectorate's vulnerability would have also given access to sensitive libraries containing evidence under legal hold for statutory planning inquiries and appeals. The security researcher noted that the option for ransomware attacks, data encryption, or data theft was readily available. However, the Planning Inspectorate's cyber monitoring tools detected the researcher's activity, and the agency fixed the vulnerability within 20 minutes of the report, verifying that no data breach occurred.
The issue with the Planning Inspectorate's vulnerability is attributed to internal housekeeping failures when using public tools, rather than open source security concerns. Amanda Brock, CEO of OpenUK, emphasized that the exposed data resulted from a failure to follow good process, which is not an open source security issue. The Planning Inspectorate has reviewed and strengthened its systems and processes to prevent similar issues from recurring.
The discovery of vulnerabilities in UK government code has sparked arguments about the practice of publishing source code in the open, particularly with the accelerated vulnerability discovery enabled by AI. Some organizations, such as the NHS, have reportedly ordered technology teams to transition away from open source code due to security concerns. However, the issue at hand appears to be more related to poor cyber hygiene and neglect of technology maintenance rather than the open source approach itself.
The security researcher's findings have prompted the affected organizations to address the vulnerabilities, with several departments, including the Department of Education, fixing the issues in their codebases. The Scottish Government has also dealt with a vulnerability in its open data portal, which would have allowed visitors to read administrative account information and change site configuration. The incident highlights the need for improved cyber hygiene and maintenance practices within the UK government's technology estate.
Questions and answers
What caused the security vulnerabilities in UK government code?
The vulnerabilities were caused by poor cyber hygiene and neglect of technology maintenance, as well as internal housekeeping failures when using public tools.
How did the security researcher discover the vulnerabilities?
The researcher used consumer-grade AI models on a laptop to discover the vulnerabilities, indicating that the issues could have been identified through routine IT health checks.
What actions have the affected organizations taken to address the vulnerabilities?
The affected organizations, including the Department of Education and the Scottish Government, have fixed the issues in their codebases, and the Planning Inspectorate has reviewed and strengthened its systems and processes to prevent similar issues from recurring.



