CVE-2024-46636
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNASA Earth Observing System Data and Information System (EOSDIS) MODAPS v8.1 was discovered to contain a SQL injection vulnerability in the category parameter
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in the category parameter of NASA EOSDIS MODAPS v8.1 allows attackers to inject malicious SQL queries, potentially enabling unauthorized data access, modification, or deletion of database contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify MODAPS installationLocate the NASA EOSDIS MODAPS application on the system. Check for installed packages, services, or web applications named 'modaps', 'MODAPS', or associated with NASA's EOSDIS data processing.Affected if The system has NASA EOSDIS MODAPS software installed.
-
Check MODAPS versionDetermine the installed version of MODAPS by examining application metadata, version files, or using system commands like 'rpm -q', 'dpkg -l', or checking the application's About/Version page.Affected if The installed version is v8.1 or falls within the v8.x branch where the vulnerability exists.
-
Verify category parameter exposureIdentify if the application exposes a web interface or API endpoint that accepts a 'category' parameter. Review application routing, form inputs, or API endpoints that handle user-supplied category values.Affected if The 'category' parameter is accessible as a user-controllable input via HTTP GET/POST requests.
-
Inspect database query handling for categoryExamine the application source code or configuration that processes the 'category' parameter. Look for direct string concatenation in SQL queries rather than parameterized queries or prepared statements.Affected if The application constructs SQL queries using the category parameter through string concatenation or direct interpolation without sanitization.
-
Check for input validation mechanismsReview application logs, WAF configurations, or intrusion detection systems for any blocked SQL injection attempts targeting the category parameter. Verify if input validation or escaping is applied.Affected if No input validation, sanitization, or parameterized queries are implemented for the category parameter.
A system is affected if it runs NASA EOSDIS MODAPS v8.1 (or vulnerable v8.x versions) with an exposed 'category' parameter that is processed through unsanitized SQL queries.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement parameterized queries/prepared statements for all database operations using the category parameter. Apply input validation and escaping as defense-in-depth.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46636 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data