|
You can search for vulnerabilities managed by JVN (Japan Vulnerability Note) and NVD (National Vulnerability Database). |
Update Date":May 8, 2026, 2:21 p.m.
| No | CVSS | Level Attach Vector |
Vendor Name | Project Name | Title | CWE | CVE | Update Date | Publication Date | Impact Show |
Exploit PoC Search |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 254771 | 6.8 | 警告 | マイクロソフト | - | Microsoft Windows の kernel における権限を取得される脆弱性 |
CWE-20
不適切な入力確認 |
CVE-2009-1127 | 2010-01-4 15:24 | 2009-11-10 | Show | GitHub Exploit DB Packet Storm |
| 254772 | 10 | 危険 | マイクロソフト | - | Microsoft Windows の License Logging Server (llssrv.exe) における任意のコードを実行される脆弱性 |
CWE-119
バッファエラー |
CVE-2009-2523 | 2010-01-4 15:24 | 2009-11-10 | Show | GitHub Exploit DB Packet Storm |
| 254773 | 9.3 | 危険 | マイクロソフト | - | Microsoft Windows の Web Services on Devices API (WSDAPI) における任意のコードを実行される脆弱性 |
CWE-94
コード・インジェクション |
CVE-2009-2512 | 2010-01-4 15:23 | 2009-11-10 | Show | GitHub Exploit DB Packet Storm |
| 254774 | 10 | 危険 | アップル VMware サン・マイクロシステムズ |
- | Sun Java SE の Provider クラスにおける詳細不明な脆弱性 |
CWE-noinfo
情報不足 |
CVE-2009-2722 | 2010-01-4 14:56 | 2009-08-10 | Show | GitHub Exploit DB Packet Storm |
| 254775 | 10 | 危険 | アップル VMware サン・マイクロシステムズ |
- | Sun Java SE の Provider クラスにおける詳細不明な脆弱性 |
CWE-noinfo
情報不足 |
CVE-2009-2723 | 2010-01-4 14:55 | 2009-08-10 | Show | GitHub Exploit DB Packet Storm |
Update Date:May 8, 2026, 4:54 a.m.
| No | CVSS | Level Attach Vector |
Vendor Name | Project Name | Title | CWE | CVE | Update Date | Publication Date | Show Affected | Exploit PoC Search |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 315071 | 9.8 |
CRITICAL
Network |
- | - | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | - | CVE-2023-48719 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315072 | 9.8 |
CRITICAL
Network |
- | - | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | - | CVE-2023-48717 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315073 | 8.8 |
HIGH
Network |
- | - | Rejected reason: It is a duplicate. | - | CVE-2023-45127 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315074 | 8.8 |
HIGH
Network |
- | - | Rejected reason: It is a duplicate. | - | CVE-2023-45126 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315075 | 8.8 |
HIGH
Network |
- | - | Rejected reason: It is a duplicate. | - | CVE-2023-45125 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315076 | 8.8 |
HIGH
Network |
- | - | Rejected reason: It is a duplicate. | - | CVE-2023-45124 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315077 | 8.8 |
HIGH
Network |
- | - | Rejected reason: It is a duplicate. | - | CVE-2023-45123 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315078 | 8.8 |
HIGH
Network |
- | - | Rejected reason: It is a duplicate. | - | CVE-2023-45122 | 2024-01-3 01:15 | 2023-12-22 | Show | GitHub Exploit DB Packet Storm |
| 315079 | 6.1 |
MEDIUM
Network |
- | - | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | - | CVE-2023-5306 | 2024-01-3 01:15 | 2023-11-1 | Show | GitHub Exploit DB Packet Storm |
| 315080 | 6.1 |
MEDIUM
Network |
- | - | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. | - | CVE-2023-44486 | 2024-01-3 01:15 | 2023-11-1 | Show | GitHub Exploit DB Packet Storm |