Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Dependencies are parts, written by other people, that your own program uses. Typical examples are WordPress plugins and themes, and packages brought in through npm or Composer. If the part has a hole, the site that built it in has the same hole.
How do dependencies work?
Think of assembling furniture. You do not plane the boards yourself. You buy ready-made handles and hinges and fit them. Building a site is the same: almost nobody writes features such as login, payment, and email sending from scratch each time. They borrow useful parts and combine them.
A part may itself borrow other parts. Because the way parts call other parts is nested, the whole set of parts you use tends to be larger than it looks. In MITRE CWE's explanation, an example is Log4j, a Java logging part that sits deep inside other parts.
When a vulnerability is published, it gets a worldwide number (CVE) and the affected parts and versions are announced. CWE notes that when the Log4j vulnerability was announced, many organizations struggled to count which of their products were affected. The problems that holes in parts cause are explained in vulnerable dependencies.
Why do dependencies matter?
Because a hole in a part becomes a hole in your own site as it is. OWASP gives examples of states that make a site vulnerable: you do not know the parts you use and their versions, a part is old and no longer supported, you do not check for vulnerabilities regularly, and updates are late.
The path of countermeasures is clear. First, remove parts you do not use. Next, keep a continuing list of the parts and versions in use, and watch for published vulnerability information. OWASP also recommends getting parts from official sources and choosing signed packages.
MITRE CWE lists, among its countermeasures, keeping a software bill of materials (SBOM) and deciding who is responsible for updates. If you leave this to an agency, check again who does the updating. Our Cyber Shield Guard checks the known vulnerabilities of plugins and themes against its data every day.
How should you keep track of your parts?
- Write down every plugin, theme, and package, with versions.
- Delete any you do not use.
- Name who updates each one and how often.
- Watch for published vulnerabilities in the ones you keep.
For help drawing up the list, contact us.
Related terms
- Vulnerability: a security hole that can hide in a part
- CVE: the worldwide number that identifies a hole
Frequently asked questions
Is it a problem to leave plugins installed that I do not use?
Yes. Even if unused, as long as they sit on the site, any holes in them remain. OWASP also lists removing unused dependencies, features, components, and files first among its countermeasures.
How can I find out what parts my site uses?
For WordPress, the list of plugins and themes in the admin screen is the starting point. For a system you developed yourself, management tools such as npm and Composer can list the parts in use and their versions. Keep updating a list that includes the parts those parts call.
I worry an update will break the site. What should I do?
Take a backup before updating and, if you can, check behavior in a test place with the same setup as production. While a part cannot be updated in a hurry, a mechanism that stops traffic at the entrance can buy time. The real countermeasure, though, is updating.
Next step
The free URL check shows only what is visible from outside, so it cannot list the parts inside your site. For help with making the list and planning updates, contact us. A detailed explanation is in vulnerable dependencies.
Frequently asked questions
Is it a problem to leave plugins installed that I do not use?
Yes. Even if unused, as long as they sit on the site, any holes in them remain. OWASP also lists removing unused dependencies, features, components, and files first among its countermeasures.
How can I find out what parts my site uses?
For WordPress, the list of plugins and themes in the admin screen is the starting point. For a system you developed yourself, management tools such as npm and Composer can list the parts in use and their versions. Keep updating a list that includes the parts those parts call.
I worry an update will break the site. What should I do?
Take a backup before updating and, if you can, check behavior in a test place with the same setup as production. While a part cannot be updated in a hurry, a mechanism that stops traffic at the entrance can buy time. The real countermeasure, though, is updating.