LiveActive security incident?Get immediate response
CVE Record

CVE-2009-2357: The default configuration of TekRADIUS 3.0 uses the sa account to communicate with Microsoft SQL Server, wh...

The default configuration of TekRADIUS 3.0 uses the sa account to communicate with Microsoft SQL Server, which makes it easier for remote attackers to obtain privileged access to the database and the underlying Windows operating system.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

TekRADIUS 3.0 reportedly shipped with a risky default database configuration: it used Microsoft SQL Server's highly privileged sa account. If left unchanged, compromise of the RADIUS application path could give an attacker privileged database access and potentially Windows operating-system access. Exposure is most likely in legacy TekRADIUS 3.0 deployments that still use Microsoft SQL Server with default database credentials or sa-based application connectivity. Treat this as a high-priority legacy configuration risk if TekRADIUS 3.0 remains in use. The main concern is excessive privilege, not confirmed active exploitation. Mitigation focus: Check vendor guidance for TekRADIUS 3.0 remediation or upgrade options.; Replace sa application access with a least-privileged SQL account where supported.; Restrict SQL Server access to only required trusted hosts..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2009-2357 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.