Skip to content
Fencer Intel
low 1.2

CVE-2013-4476 json

Samba 4.0.x before 4.0.11 and 4.1.x before 4.1.1, when LDAP or HTTP is provided over SSL, uses world-readable permissions for a private key…

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

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

Summary

Samba 4.0.x before 4.0.11 and 4.1.x before 4.1.1, when LDAP or HTTP is provided over SSL, uses world-readable permissions for a private key, which allows local users to obtain sensitive information by reading the key file, as demonstrated by access to the local filesystem on an AD domain controller.

Patch / fix

  • samba Debian 14, Debian 13, Debian 12 2:4.0.11+dfsg-1

debian advisories DEBIAN-CVE-2013-4476

  • samba openSUSE Tumbleweed 4.5.0-1.1

opensuse advisories openSUSE-SU-2024:10069-1

Is CVE-2013-4476 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-4476 updated cvss 3.6

samba: world-readable key.pem with Samba 4 AD DC

  • Red Hat Enterprise Linux 5 samba, samba3x Red Hat Enterprise Linux 6 samba, samba-swat, libsmbclient, samba-client, samba-common, samba-winbind, +4 more Red Hat Enterprise Linux 7 ctdb, samba, samba-dc, ctdb-tests, samba-libs, samba-pidl, +18 more Red Hat Storage 2 samba
    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

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

CVSS scores

assigned by version score vector
NVD 2.0 1.2 AV:L/AC:H/Au:N/C:P/I:N/A:N

Classification

Weakness

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.