Skip to content
Fencer Intel
medium 4.3

CVE-2013-1841 json

Net-Server, when the reverse-lookups option is enabled, does not check if the hostname resolves to the source IP address, which might allow…

published 12y ago modified 4mo ago also EUVD-2013-1850

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

Net-Server, when the reverse-lookups option is enabled, does not check if the hostname resolves to the source IP address, which might allow remote attackers to bypass ACL restrictions via the hostname parameter.

Patch / fix

  • libnet-server-perl Debian 14, Debian 13, Debian 12 2.013-1

debian advisories DEBIAN-CVE-2013-1841

  • perl-Net-Server SLES for SAP 12 SP5, SLES 12 SP5 2.007-5.3.1
  • perl-Net-Server SLE Real Time 15 SP3, SLE Module for Basesystem 15 SP4, openSUSE Leap 15.4 2.009-150000.3.3.1

suse advisories SUSE-SU-2023:0759-1SUSE-SU-2023:0746-1

Is CVE-2013-1841 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-1841 updated cvss 4.3

perl-Net-Server: Improper reverse DNS matching check for the given hostname

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.94% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.