PCRE before 8.38 mishandles the (?(<digits>) and (?(R<digits>) conditions, which allows remote attackers to cause a denial of service (integer overflow) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Link | Tags |
---|---|
http://www.openwall.com/lists/oss-security/2015/11/29/1 | third party advisory mailing list |
http://www.securityfocus.com/bid/82990 | vdb entry third party advisory |
http://lists.fedoraproject.org/pipermail/package-announce/2016-January/174931.html | mailing list third party advisory vendor advisory |
https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05240731 | third party advisory |
https://bto.bluecoat.com/security-advisory/sa128 | third party advisory permissions required |
http://vcs.pcre.org/pcre/code/trunk/ChangeLog?view=markup | broken link |
https://security.gentoo.org/glsa/201607-02 | third party advisory vendor advisory |
https://security.netapp.com/advisory/ntap-20230216-0002/ |