CVE-2006-3013

UnknownEPSS 2.05%

Last modified

CVE-2006-3013 is a vulnerability of currently unknown severity. Interpretation conflict in resetpw.php in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL commands via an email parameter containing a null (%00) character after a valid e-mail address, which passes the validation check in the eregi PHP command. NOTE: it could be argued that this vulnerability is due to a bug in the eregi PHP command and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in phpBannerExchange.. EPSS estimates a 2.05% chance of exploitation in the next 30 days.

Description

Interpretation conflict in resetpw.php in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL commands via an email parameter containing a null (%00) character after a valid e-mail address, which passes the validation check in the eregi PHP command. NOTE: it could be argued that this vulnerability is due to a bug in the eregi PHP command and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in phpBannerExchange.

Metrics

EPSS Probability
2.05%

78.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
Eschew.NetPhpbannerexchange2.0
Eschew.NetPhpbannerexchange2.0_update_1
Eschew.NetPhpbannerexchange2.0_update_2
Eschew.NetPhpbannerexchange2.0_update_3
Eschew.NetPhpbannerexchange2.0_update_4
Eschew.NetPhpbannerexchange2.0_update_5

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2006-3013?
Interpretation conflict in resetpw.php in phpBannerExchange before 2.0 Update 6 allows remote attackers to execute arbitrary SQL commands via an email parameter containing a null (%00) character after a valid e-mail address, which passes the validation check in the eregi PHP command. NOTE: it could be argued that this vulnerability is due to a bug in the eregi PHP command and the proper fix should be in PHP; if so, then this should not be treated as a vulnerability in phpBannerExchange.
How severe is CVE-2006-3013?
Severity scoring for CVE-2006-3013 is pending analysis. The EPSS model estimates a 2.05% probability of exploitation in the next 30 days.
How do I fix CVE-2006-3013?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2006-3013?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST