squid: /usr/sbin/pinger packaged with wrong permission
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.33% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: squid (openSUSE:Leap 15.0) 4.9-lp150.13.1; permissions (openSUSE:Leap 15.1) 20181116-lp151.4.9.1; squid (openSUSE:Leap 15.1) 4.9-lp151.2.7.1.
- Severity is disputed: the assigning authority (CNA) scores it 5.1, NVD 7.1.
Low priority for now. Upgrade to squid (openSUSE:Leap 15.0) 4.9-lp150.13.1; permissions (openSUSE:Leap 15.1) 20181116-lp151.4.9.1; squid (openSUSE:Leap 15.1) 4.9-lp151.2.7.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The /usr/sbin/pinger binary packaged with squid in SUSE Linux Enterprise Server 15 before and including version 4.8-5.8.1 and in SUSE Linux Enterprise Server 12 before and including 3.5.21-26.17.1 had squid:root, 0750 permissions. This allowed an attacker that compromissed the squid user to gain persistence by changing the binary
- Published
- Oct 7, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-276
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 7.1
- CNA · suse
- 5.1
- 2.0 point gap
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| suse | suse linux enterprise server | cpe:2.3:o:suse:suse_linux_enterprise_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- suse suse linux enterprise server12
- suse suse linux enterprise server15
Versions reported by the vendor
Affected version ranges reported by the assigning authority (suse). Independent of NVD's CPE analysis and usually ahead of it.
SUSE SUSE Linux Enterprise Server 12
- squid and later · up to and including 3.5.21-26.17.1affected
SUSE SUSE Linux Enterprise Server 15
- squid and later · up to and including 4.8-5.8.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.0 | squid | before 4.9-lp150.13.1 | 4.9-lp150.13.1 |
| openSUSE:Leap 15.1 | permissions | before 20181116-lp151.4.9.1 | 20181116-lp151.4.9.1 |
| openSUSE:Leap 15.1 | squid | before 4.9-lp151.2.7.1 | 4.9-lp151.2.7.1 |
| openSUSE:Leap 15.3 | permissions | before 20200127-lp153.24.3.1 | 20200127-lp153.24.3.1 |
| openSUSE:Tumbleweed | permissions | before 1550_20210901.1550-29.2 | 1550_20210901.1550-29.2 |
| SUSE:HPE Helion OpenStack 8 | permissions | before 2015.09.28.1626-17.20.1 | 2015.09.28.1626-17.20.1 |
| SUSE:Linux Enterprise Desktop 12 SP4 | permissions | before 20170707-3.14.1 | 20170707-3.14.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | permissions | before 20180125-3.21.1 | 20180125-3.21.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | permissions | before 20180125-3.18.1 | 20180125-3.18.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 | squid | before 4.9-5.11.1 | 4.9-5.11.1 |
| SUSE:Linux Enterprise Server 12 SP5 | permissions | before 20170707-6.4.1 | 20170707-6.4.1 |
Same product
suse: all recordsOther highest-scoring records for the same primary product.
- CVE-2011-3172unix2_chkpwd do not check for a valid account39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:permissions | 20181116-lp151.4.9.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:squid | 4.9-lp150.13.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:permissions | 2015.09.28.1626-17.20.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
| suse:squid | 4.9-5.11.1 · SUSE:Linux Enterprise Module for Server Applications 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-276 · Incorrect Default PermissionsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.