CVE-2018-1283: In Apache httpd 2.4.0 to 2.4.29, when mod_session is configured to forward its session data to CGI applications (SessionEnv on, not the…
Noroxi assessment
Priority: Monitor (action score 24/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: 9.7% (FIRST EPSS); higher than 95.5% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: apache2 (Alpine:v3.10) 2.4.33-r0; apache2 (Debian:12) 2.4.33-1; apache2 (Debian:8) 2.4.10-10+deb8u12.
Low priority for now. Upgrade to apache2 (Alpine:v3.10) 2.4.33-r0; apache2 (Debian:12) 2.4.33-1; apache2 (Debian:8) 2.4.10-10+deb8u12 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
In Apache httpd 2.4.0 to 2.4.29, when mod_session is configured to forward its session data to CGI applications (SessionEnv on, not the default), a remote user may influence their content by using a "Session" header. This comes from the "HTTP_SESSION" variable name used by mod_session to forward its data to CGIs, since the prefix "HTTP_" is also used by the Apache HTTP Server to pass HTTP header fields, per CGI specifications.
- Published
- Mar 26, 2018
- Updated
- Jun 16, 2026
- EPSS
- 9.7% · 95th percentile
- CWE
- —
Report tools
Action score
24
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.7%
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 Apache HTTP Server on your server exposed to the internet?Run a port scan
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 |
|---|---|---|
| apache | http server | cpe:2.3:a:apache:http_server |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| netapp | santricity cloud connector | cpe:2.3:a:netapp:santricity_cloud_connector |
| netapp | storage automation store | cpe:2.3:a:netapp:storage_automation_store |
| netapp | storagegrid | cpe:2.3:a:netapp:storagegrid |
| netapp | clustered data ontap | cpe:2.3:o:netapp:clustered_data_ontap |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Using http server? Add it to your stack and be the first to know about CVEs like this one. (Apache HTTP)
Is Apache HTTP Server on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanVersions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Software Foundation Apache HTTP Server
- 2.4.0 to 2.4.29affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache http server2.4.0 and later · up to 2.4.29 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | apache2 | before 2.4.33-r0 | 2.4.33-r0 |
| Debian:12 | apache2 | before 2.4.33-1 | 2.4.33-1 |
| Debian:8 | apache2 | before 2.4.10-10+deb8u12 | 2.4.10-10+deb8u12 |
| Debian:9 | apache2 | before 2.4.25-3+deb9u4 | 2.4.25-3+deb9u4 |
| Red Hat:enterprise_linux:7::client | httpd | before 0:2.4.6-95.el7 | 0:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | httpd-debuginfo | before 0:2.4.6-95.el7 | 0:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | httpd-devel | before 0:2.4.6-95.el7 | 0:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | httpd-manual | before 0:2.4.6-95.el7 | 0:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | httpd-tools | before 0:2.4.6-95.el7 | 0:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | mod_ldap | before 0:2.4.6-95.el7 | 0:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | mod_proxy_html | before 1:2.4.6-95.el7 | 1:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | mod_session | before 0:2.4.6-95.el7 | 0:2.4.6-95.el7 |
| Red Hat:enterprise_linux:7::client | mod_ssl | before 1:2.4.6-95.el7 | 1:2.4.6-95.el7 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24 | before 0:1-6.jbcs.el6 | 0:1-6.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apache-commons-daemon-jsvc | before 1:1.1.0-3.redhat_2.jbcs.el6 | 1:1.1.0-3.redhat_2.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apache-commons-daemon-jsvc-debuginfo | before 1:1.1.0-3.redhat_2.jbcs.el6 | 1:1.1.0-3.redhat_2.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr | before 0:1.6.3-31.jbcs.el6 | 0:1.6.3-31.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-debuginfo | before 0:1.6.3-31.jbcs.el6 | 0:1.6.3-31.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-devel | before 0:1.6.3-31.jbcs.el6 | 0:1.6.3-31.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-util | before 0:1.6.1-24.jbcs.el6 | 0:1.6.1-24.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-util-debuginfo | before 0:1.6.1-24.jbcs.el6 | 0:1.6.1-24.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-util-devel | before 0:1.6.1-24.jbcs.el6 | 0:1.6.1-24.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-util-ldap | before 0:1.6.1-24.jbcs.el6 | 0:1.6.1-24.jbcs.el6 |
| Red Hat:jboss_core_services:1::el6 | jbcs-httpd24-apr-util-mysql | before 0:1.6.1-24.jbcs.el6 | 0:1.6.1-24.jbcs.el6 |
+76
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-42013Path Traversal and Remote Code Execution in Apache HTTP Server 2.4.49 and 2.4.50 (incomplete fix of CVE-2021-41773)KEV99Now
- CVE-2021-41773Path traversal and file disclosure vulnerability in Apache HTTP Server 2.4.49KEV99Now
- CVE-2024-38475Apache HTTP Server weakness in mod_rewrite when first segment of substitution matches filesystem path.KEV96Now
Published before and after this one in the same product
- ← EarlierCVE-2017-15710Mar 26, 2018 · In Apache httpd 2.0.23 to 2.0.65, 2.2.0 to 2.2.34, and 2.4.0 to 2.4.29, mod_authnz_ldap, if configured with AuthLDAPCharsetConfig, uses the…35Monitor
- ← EarlierCVE-2017-15715Mar 26, 2018 · In Apache httpd 2.4.0 to 2.4.29, the expression specified in <FilesMatch> could match '$' to a newline character in a malicious filename…58Plan
- Later →CVE-2018-1301Mar 26, 2018 · A specially crafted request could have crashed the Apache HTTP Server prior to version 2.4.30, due to an out of bound access after a size…27Monitor
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 |
|---|---|---|
| alpine:apache2 | 2.4.33-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:apache2 | 2.4.33-1 · Debian:12 | Package registry (OSV) |
| red hat:jbcs-httpd24 | 0:1-6.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apache-commons-daemon-jsvc | 1:1.1.0-3.redhat_2.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apache-commons-daemon-jsvc-debuginfo | 1:1.1.0-3.redhat_2.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr | 0:1.6.3-31.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-debuginfo | 0:1.6.3-31.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-devel | 0:1.6.3-31.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util | 0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util-debuginfo | 0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util-devel | 0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util-ldap | 0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util-mysql | 0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| red hat:jbcs-httpd24-apr-util-nss | 0:1.6.1-24.jbcs.el6 · Red Hat:jboss_core_services:1::el6 | Package registry (OSV) |
| suse:apache2 | 2.4.16-20.16.1 · SUSE:OpenStack Cloud 6 | 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
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
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 (19 more)Show less
- www.securityfocus.com/bid/103520
- www.securitytracker.com/id/1040568
- access.redhat.com/errata/RHSA-2018:3558
- access.redhat.com/errata/RHSA-2019:0366
- access.redhat.com/errata/RHSA-2019:0367
- httpd.apache.org/security/vulnerabilities_24.html
- lists.apache.org/thread.html/56c2e7cc9deb1c12a843d0dc251ea7fd3e7e80293cde02fcd65286ba%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/84a3714f0878781f6ed84473d1a503d2cc382277e100450209231830%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/r06f0d87ebb6d59ed8379633f36f72f5b1f79cadfda72ede0830b42cf%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/r15f9aa4427581a1aecb4063f1b4b983511ae1c9935e2a0a6876dad3c%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/r6521a7f62276340eabdb3339b2aa9a38c5f59d978497a1f794af53be%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/r76142b8c5119df2178be7c2dba88fde552eedeec37ea993dfce68d1d%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/r9f93cf6dde308d42a9c807784e8102600d0397f5f834890708bf6920%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/rc998b18880df98bafaade071346690c2bc1444adaa1a1ea464b93f0a%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/rd18c3c43602e66f9cdcf09f1de233804975b9572b0456cc582390b6f%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/rd336919f655b7ff309385e34a143e41c503e133da80414485b3abcc9%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/re3d27b6250aa8548b8845d314bb8a350b3df326cacbbfdfe4d455234%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/rf6449464fd8b7437704c55f88361b66f12d5b5f90bcce66af4be4ba9%40%3Ccvs.httpd.apache.org%3E
- lists.apache.org/thread.html/rfcf929bd33a6833e3f0c35eebdad70d5060665f9c4e17ea467c66770%40%3Ccvs.httpd.apache.org%3E
Vendor advisories and official records. Exploit/PoC links are deliberately left out.