Skip to main content
No exploitation reported

CVE-2009-2272

No exploitation reported by the sources we read.

  • Published2009-07-01
  • WeaknessCWE-312

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The Huawei D100 stores the administrator's account name and password in cleartext in a cookie, which allows context-dependent attackers to obtain sensitive information by (1) reading a cookie file, by (2) sniffing the network for HTTP headers, and possibly by using unspecified other vectors.

Timeline

dates in UTC
  1. 2009-07-0113:00CVE publishedNVD

Versions per branch

NVD
Huawei d100 firmwareversion to verify
BranchAffectedFixed in
—all versionsno fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2009-07-01
Last Modified
2026-06-16
NVD status
Modified
GitHub Advisory
GHSA-6c5q-h46j-p8gq

Frequently asked questions

What is CVE-2009-2272?

The Huawei D100 stores the administrator's account name and password in cleartext in a cookie, which allows context-dependent attackers to obtain sensitive information by (1) reading a cookie file, by (2) sniffing the network for HTTP headers, and possibly by using unspecified other vectors.

Is CVE-2009-2272 actively exploited?

Active exploitation of CVE-2009-2272 has not been confirmed. Its EPSS score was 0.6% on 2026-11-16, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2009-2272?

CVE-2009-2272 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Sources for this record