CVE-2005-1850: Certain contributed scripts for ekg Gadu Gadu client 1.5 and earlier create temporary files insecurely, with unknown impact and attack…
Noroxi assessment
Priority: Plan (action score 40/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: 1.5% (FIRST EPSS); higher than 74.8% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: ekg (Debian:3.1) 1:1.5+20050411-4; ekg (Debian:4.0) 1:1.5+20050808+1.6rc3-0etch1.
Add it to your regular patch cycle. Upgrade to ekg (Debian:3.1) 1:1.5+20050411-4; ekg (Debian:4.0) 1:1.5+20050808+1.6rc3-0etch1 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
Certain contributed scripts for ekg Gadu Gadu client 1.5 and earlier create temporary files insecurely, with unknown impact and attack vectors, a different vulnerability than CVE-2005-1916.
- Published
- Jul 19, 2005
- Updated
- Jun 16, 2026
- EPSS
- 1.5% · 74th percentile
- CWE
- —
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
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.
Is your version affected? Check itNoroxi 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 |
|---|---|---|
| ekg | ekg | cpe:2.3:a:ekg:ekg |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ekg ekg1.0
- ekg ekg1.0_rc2
- ekg ekg1.0_rc3
- ekg ekg1.1
- ekg ekg1.1_rc1
- ekg ekg1.1_rc2
- ekg ekg1.3
- ekg ekg1.4
+3 more rows
- ekg ekg1.5
- ekg ekg1.5_rc1
- ekg ekg1.5_rc2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:3.1 | ekg | before 1:1.5+20050411-4 | 1:1.5+20050411-4 |
| Debian:4.0 | ekg | before 1:1.5+20050808+1.6rc3-0etch1 | 1:1.5+20050808+1.6rc3-0etch1 |
Same product
ekg: all recordsOther highest-scoring records for the same primary product.
- CVE-2005-1851A certain contributed script for ekg Gadu Gadu client 1.5 and earlier allows attackers to execute shell commands via unknown attack vectors.40Plan
- CVE-2005-2369Multiple integer signedness errors in libgadu, as used in ekg before 1.6rc2 and other packages, may allow remote attackers to cause a…31Monitor
- CVE-2005-1852Multiple integer overflows in libgadu, as used in Kopete in KDE 3.2.3 to 3.4.1, ekg before 1.6rc3, GNU Gadu, CenterICQ, Kadu, and other…31Monitor
Published before and after this one in the same product
- Later →CVE-2005-2370Jul 26, 2005 · Multiple "memory alignment errors" in libgadu, as used in ekg before 1.6rc2, Gaim before 1.5.0, and other packages, allows remote attackers…21Monitor
- Later →CVE-2005-2448Aug 3, 2005 · Multiple "endianness errors" in libgadu in ekg before 1.6rc2 allow remote attackers to cause a denial of service (invalid behavior in…21Monitor
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 |
|---|---|---|
| debian:ekg | 1:1.5+20050411-4 · Debian:3.1 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
—
CVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.