Http Sms Gateway
Vendor:
First CVE: Dec 21, 2006 · Active for 19 years
1
Total CVEs
Bottom 1%
1.0
Avg CVEs / Year
Bottom 1%
2.1
Avg CVSS
Bottom 1%
0.0%
KEV Rate
Bottom 1%
Trends Over Time
The number and severity of CVEs published that impact Http Sms Gateway over time
Volume of CVEsAvg CVSS Base Score
First CVE
Dec 21, 2006
19 years ago
Most Recent CVE
Dec 21, 2006
7,158 days ago
CVE Severity & Scoring
Http Sms Gateway1 CVEs
100%
All CVEs352,785 CVEs
45%
40%
11%
Low
Attack Vector
Local0 (0.0%)
Network0 (0.0%)
Unknown1 (100.0%)
Physical0 (0.0%)
Adjacent Network0 (0.0%)
Attack Complexity
Low0 (0.0%)
High0 (0.0%)
Unknown1 (100.0%)
User Interaction
None0 (0.0%)
Unknown1 (100.0%)
Required0 (0.0%)
Privileges Required
Low0 (0.0%)
High0 (0.0%)
None0 (0.0%)
Unknown1 (100.0%)
Top CVEs
Signals from CVEs in this product scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
Ozeki HTTP-SMS Gateway 1.0, and possibly earlier, stores usernames and passwords in plaintext in the HKLM\Software\Ozeki\SMSServer\CurrentVersion\Plugins\httpsmsgate registry key, | Dec 21, 2006 | 2.1 | 11 | NO | NO |
Exploit Exposure
Signals from CVEs in this product scope (1 CVEs).
CISA KEV
0 CVEs
0.0% of CVEs· Bottom 1%
Metasploit
0 CVEs
0.0% of CVEs· Bottom 1%
Nuclei
0 CVEs
0.0% of CVEs· Bottom 1%
ExploitDB
0 CVEs
0.0% of CVEs· Bottom 1%
Social Chatter
Signals from CVEs in this product scope (1 CVEs).
Media Mentions
Signals from CVEs in this product scope (1 CVEs).
Top CNAs Publishing CVEs For Http Sms Gateway
Versions
No cataloged versions.