CVE-2019-3871
Last modified
CVE-2019-3871 is a medium-severity vulnerability rated 6.5/10 on the CVSS scale. A vulnerability was found in PowerDNS Authoritative Server before 4.0.7 and before 4.1.7. An insufficient validation of data coming from the user when building a HTTP request from a DNS query in the HTTP Connector of the Remote backend, allowing a remote user to cause a denial of service by making the server connect to an invalid endpoint, or possibly information disclosure by making the server connect to an internal endpoint and somehow extracting meaningful information about the response. EPSS estimates a 12.86% chance of exploitation in the next 30 days.
Description
A vulnerability was found in PowerDNS Authoritative Server before 4.0.7 and before 4.1.7. An insufficient validation of data coming from the user when building a HTTP request from a DNS query in the HTTP Connector of the Remote backend, allowing a remote user to cause a denial of service by making the server connect to an invalid endpoint, or possibly information disclosure by making the server connect to an internal endpoint and somehow extracting meaningful information about the response
Metrics
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Powerdns | Authoritative Server | < 4.0.7 |
| Powerdns | Authoritative Server | >= 4.1.0, < 4.1.7 |
| Fedoraproject | Fedora | 28 |
| Fedoraproject | Fedora | 29 |
References
- http://www.openwall.com/lists/oss-security/2019/03/18/4Exploit, Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/107491Third Party Advisory, VDB Entry
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3871Exploit, Issue Tracking, Patch, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2019/03/18/4Exploit, Mailing List, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/107491Third Party Advisory, VDB Entry
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3871Exploit, Issue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-3871?
How severe is CVE-2019-3871?
How do I fix CVE-2019-3871?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2019
- CVE-2019-3865A vulnerability was found in quay-2, where a stored XSS vuln…6.1
- CVE-2019-3866An information-exposure vulnerability was discovered where o…5.5
- CVE-2019-3867A vulnerability was found in the Quay web application. Sessi…4.1
- CVE-2019-3868Keycloak up to version 6.0.0 allows the end user token (acce…3.8
- CVE-2019-3869When running Tower before 3.4.3 on OpenShift or Kubernetes, …7.2
- CVE-2019-3870A vulnerability was found in Samba from version (including) …6.1
- CVE-2019-3872It was found that a SAMLRequest containing a script could be…5.4
- CVE-2019-3873It was found that Picketlink as shipped with Jboss Enterpris…6.4
- CVE-2019-3874The SCTP socket buffer used by a userspace application is no…6.5
- CVE-2019-3875A vulnerability was found in keycloak before 6.0.2. The X.50…6.5
- CVE-2019-3876A flaw was found in the /oauth/token/request custom endpoint…6.3
- CVE-2019-3877A vulnerability was found in mod_auth_mellon before v0.14.2.…5.8
Are you affected by CVE-2019-3871?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
