Attack methods and causes
Vulnerability
A security flaw in a device or program. Attackers can use it to get in, steal information or take control.
How it works
A vulnerability is a security flaw caused by a mistake in the basic software of a computer or phone (its operating system), in an app or in the software inside a device. It is also called a security hole. Vulnerabilities are found not only in computers and phones but also in devices such as the boxes that connect a home or office to the internet (routers) and in home appliances. [1] [2]
When one is found, the maker usually releases a fixed version or patch. New vulnerabilities keep turning up after each fix, so updating is never done once and for all. [1]
The seriousness of a published vulnerability is rated with CVSS, a scoring method used worldwide, as a score from 0 to 10.0 and a band such as critical, high, medium or low. [3]
What can happen
- A system with an unfixed vulnerability can be broken into or infected with malware. [1]
- A server open to the internet can have its website defaced, or be used by attackers as a stopover point to attack others while hiding where they really are. [1]
- Flaws in VPN devices, which let staff connect to the office computers from outside, and in similar devices are a main way in for ransomware attacks. [4]
- Software and devices whose maker no longer provides fixes (past their end of support) stay unfixed when new vulnerabilities are found. [2]
Prevention
For individuals
For organizations
- Keep a list of the systems, software and devices reachable from the internet, and a routine for checking new vulnerability reports for each. [5] [7]
- Apply patches to VPN and similar devices as soon as they are released, and replace or retire devices past their end of support. [4] [7]
- Keep the screens for changing settings (management screens) unreachable from the internet, and switch off features and network entry points (ports) that are not needed. [7]
- For connections from outside, use multi-factor authentication: a second check besides the password, such as a code on a phone. [6]
If it happens to you
- Update to a fixed version. Any device left unpatched can let attackers back in the same way. [4]
- Change the passwords of accounts used through the device in case attackers used the flaw before the update; updating does not stop logins with IDs and passwords already stolen. [4] [6]
- Look for unknown accounts and odd login attempts, and check the systems behind the device for hidden ways back in left by attackers (backdoors) or malware. [6]
On this site
This site covers a vulnerability only after Japan's vulnerability notice site JVN, the worldwide CVE list or the maker has published it, with the product, versions, severity and fix. It never shows how to attack it or lists of exposed systems. A published vulnerability alone does not show that a named organization was broken into.
Incidents where a website or app was attacked through a flaw carry the method Web app exploit. Organizations that paused services after a disclosure to avoid harm are recorded as Precautionary halt.
How precautionary halts affect severity is explained under Severity and impact levels in the guide.
Example incidents
2025-07-14[Severity: Critical][Web app exploit][Data leak]
Shinko Shuppansha Keirinkan: SQL injection at Smart LectureAn SQL injection attack on a question form may have exposed member data.
2024-07-31[Severity: Critical][Web app exploit][Data leak]
Tokyo Tamago Honpo: card data (65,387 records) and personal data (73,961 records) may have leaked from its Tokyo Tamago Gomatamago online shopAttackers used a flaw to secretly change the program behind the payment page, and about three years of card data may have leaked.
2026-10-21[Severity: Moderate][Web app exploit][Service outage]
php2shell: critical flaws in PHPDetails of critical PHP flaws spread before the fix, and many organizations paused services as a precaution.
Related terms
Sources
- [1][Regulator]脆弱性とは?MIC
- [2][Regulator]サポート切れソフトウェアを利用しないようにしようMIC
- [3][Regulator]共通脆弱性評価システムCVSS v3概説IPA
- [4][Regulator]ランサムウェア被害防止対策NPA
- [5][Regulator]2022年10月から12月を振り返ってJPCERT/CC · 2022-12-22
- [6][Regulator]Fortinet 社製 FortiOS の SSL VPN 機能の脆弱性 (CVE-2018-13379) の影響を受けるホストに関する情報の公開についてJPCERT/CC · 2020-11-27
- [7][Regulator]VPN機器等に対するORB(Operational Relay Box)化を伴うネットワーク貫通型攻撃のおそれについてIPA · 2025-10-31