Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Software integrity failures mean update files and parts are not checked to be genuine. Integrity means content has not been rewritten without permission. OWASP Top 10:2021 gathers, under this category, the lack of integrity checks when you rely on updates, important data, and CI/CD, the automated flow that builds and publishes software.
How do software integrity failures work?
Picture a pharmacy putting a delivered box on the shelf without checking its seal. If the box was swapped on the way, the receiving side cannot tell.
OWASP gives, as examples of untrusted sources, plugins, libraries, modules, and the content of a CDN. A mechanism that applies updates automatically without verifying them is an example in the same category, because if an attacker distributes their own version, it can spread to every installation that receives the same update.
MITRE's CWE-494 defines the weakness of fetching code from a remote location and running it without checking its origin or whether it was tampered with. Parts loaded from outside are covered on the third-party scripts page, and specific checks on the third-party scripts risk page.
Why do software integrity failures matter?
Even when updates and installation follow the right steps, if the contents were swapped, the damage starts inside your own company. Updates and plugins are accepted on trust, so they are not suspected and take time to notice. It is connected with knowing the state of the parts you use, as with vulnerable dependencies.
The measures OWASP gives are to confirm, with digital signatures or similar, that software and data come from the expected source and have not been rewritten. Limit where you get packages such as npm and Maven to trusted places. Reflect changes to code and settings only after review, separate the CI/CD environment, and tighten access control.
A CWE-494 measure is to sign the code you update and have the receiver verify the signature. Minimizing the permissions to run code and running it in a dedicated environment also reduce damage, though limiting the environment is said to have limited effect.
To review how your site accepts updates and plugins, contact us.
Related terms
- Third-party scripts: the risk that programs loaded from outside are tampered with.
- Vulnerable dependencies: continuing to use parts in which a hole has been found.
- Tampering: a site's contents being rewritten without permission.
- SBOM: a list of the parts used in software, like an ingredients label.
Next step
Checking the flow by which outside parts are accepted is explained in measures against supply chain attacks. The free URL check shows only what is visible from outside. For the steps for accepting updates and plugins, contact us.
Frequently asked questions
What does integrity mean here?
It means that the content of information or software has not been rewritten without permission. A software integrity failure is a state where you do not check that the software or update you received is genuine and unaltered.
If I get software from the official source, is checking unnecessary?
Getting it from the official source matters, but it is not enough alone. Use a method that confirms the content has not been rewritten, such as a signature. OWASP also advises checking by signatures and similar means.
Frequently asked questions
What does integrity mean here?
It means that the content of information or software has not been rewritten without permission. A software integrity failure is a state where you do not check that the software or update you received is genuine and unaltered.
If I get software from the official source, is checking unnecessary?
Getting it from the official source matters, but it is not enough alone. Use a method that confirms the content has not been rewritten, such as a signature. OWASP also advises checking by signatures and similar means.