CVE-2006-6227: The Core::Receive function in neonet/core.cpp for NeoEngine 0.8.2 and earlier, and CVS 3422, allow remote atta

Routine

MEDIUM 5.0DOWNGRADE

CVE-2006-6227 is a medium-severity flaw (CVSS 5.0) affecting neoengine. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Core::Receive function in neonet/core.cpp for NeoEngine 0.8.2 and earlier, and CVS 3422, allow remote attackers to cause a denial of service (engine crash) via a message with a large uiMessageLength that produces a failed memory allocation and a null pointer dereference.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	2.4% (top 16%)
CISA exploited list	No
Published	2006-12-02
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: neoengine

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2006-12-02 02:28 UTCPublished CVE record published
2026-06-16 22:32 UTCUpdated Record last modified

neoengine neoengine DOWNGRADE

Affected: 0.8.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.8.2

1. Check installed version

apt-cache policy neoengine || rpm -q neoengine || neoengine --version

2. No fixed release: DOWNGRADE to a release before 0.8.2 (Debian / Ubuntu)

apt-cache madison neoengine sudo apt install neoengine=<VERSION_BEFORE_0.8.2> sudo apt-mark hold neoengine

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list neoengine sudo dnf downgrade neoengine-<VERSION_BEFORE_0.8.2> sudo dnf versionlock add neoengine

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2006-6227?

neoengine: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2006-6227 being exploited?

CVE-2006-6227 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2006-6227 affect?

CVE-2006-6227 affects neoengine. Severity is medium (CVSS 5.0). The Core::Receive function in neonet/core.cpp for NeoEngine 0.8.2 and earlier, and CVS 3422, allow remote attackers to cause a denial of service (engine crash) via a message with a large uiMessageLength that produces a failed memory allocat

How urgent is CVE-2006-6227?

Priority 38/100. No elevated risk signals yet.

Related CVEs

CVE-2006-6226 HIGH 7.5 DOWNGRADE Multiple format string vulnerabilities in NeoEngine 0.8.2 and earlier, and CVS 3422, allow remote attackers to

References

← Back to latest CVEs